Skip to content

[twin] Polish README and MCP tool descriptions for clarity and discoverability - #2

Merged
goww7 merged 1 commit into
mainfrom
twin/mcp-readme-tool-descriptions
May 25, 2026
Merged

[twin] Polish README and MCP tool descriptions for clarity and discoverability#2
goww7 merged 1 commit into
mainfrom
twin/mcp-readme-tool-descriptions

Conversation

@goww7

@goww7 goww7 commented May 19, 2026

Copy link
Copy Markdown
Owner

What changed

README.md

  • Added a Quick start section (3 numbered steps: get key → connect → first question) right after the hero description — new users now have a direct path without hunting through the page
  • Broke the dense opening paragraph (one long run-on sentence) into two clear sentences leading with "Give your AI agent 22 tools to…"
  • Tightened the Why Halal Terminal bullets for scannability
  • Renamed client sub-headings from "One-liner: Claude Desktop" → "Claude Desktop" (cleaner)
  • Removed the redundant Then get a free API key… note that appeared mid-Install; the Quick start section handles it now

TOOLS.md

  • Added Use when: dispatch hints to all 22 tools (previously only screen_stock had one) — helps AI agents pick the right tool without ambiguity
  • Added a token-cost warning to bulk_screen: "index runs consume many tokens — check list_indices and summary before triggering a full run"
  • Tightened get_stock_info description to note it returns sector, exchange, and description data
  • Tightened generate_report description to "ready to share or save"

server.json

  • Rewrote description to lead with "22 tools for halal investing" and mention the free tier: 239 chars (within registry limits)

package.json

  • Rewrote description for npm search discoverability, leading with the concrete tool count: 256 chars (within npm limits)

What was NOT changed

  • bin/cli.mjs — no logic changes
  • CONNECT.md, EXAMPLES.md — no changes
  • All URL structures, pricing data, plan names, and feature claims — unchanged

Tests

No test suite in this repo (docs/metadata package only). bin/cli.mjs syntax is valid; the only runtime dependency (@modelcontextprotocol/sdk) is unchanged.

Human action required

None beyond review and merge. No deploy steps needed — this is docs and package metadata only.


Generated by Claude Code

…lity

- README: add Quick start section (3 steps); break dense opening paragraph
  into clearer sentences; tighten Why Halal Terminal bullets; rename
  client sub-headings to remove "One-liner:" prefix
- TOOLS.md: add "Use when:" dispatch hints to all 22 tools; add token-cost
  warning to bulk_screen; tighten get_stock_info and generate_report descriptions
- server.json: rewrite description to lead with "22 tools" and free tier
  (239 chars, within registry limits)
- package.json: rewrite description for npm search discoverability
  (256 chars, within npm limits)

No logic changes — docs and metadata only.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR polishes user-facing documentation and package/registry metadata to make Halal Terminal’s MCP tools easier to discover and use.

Changes:

  • Adds a README quick-start flow and simplifies client setup headings.
  • Adds Use when: dispatch hints across the tool reference.
  • Rewrites npm and MCP registry descriptions around the 22-tool positioning.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

File Description
README.md Adds quick start, updates intro copy, and tightens setup/benefit wording.
TOOLS.md Adds tool-selection hints and refines several tool descriptions.
server.json Updates registry description metadata.
package.json Updates npm package description metadata.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread server.json
"name": "com.halalterminal/mcp",
"title": "Halal Terminal",
"description": "Shariah-compliant stock and ETF screening across AAOIFI, DJIM, FTSE, MSCI and S&P methodologies, plus portfolio audit, zakat, dividend purification, market data, news and SEC filings — for any MCP-compatible AI agent.",
"description": "22 tools for halal investing: screen stocks and ETFs across 5 Shariah methodologies (AAOIFI, DJIM, FTSE, MSCI, S&P), audit portfolios, calculate zakat and dividend purification, fetch market data, news and SEC filings. Free tier available.",
Comment thread package.json
"name": "@halalterminal/mcp",
"version": "1.0.0",
"description": "Official Halal Terminal MCP server — Shariah-compliant stock and ETF screening across AAOIFI, DJIM, FTSE, MSCI and S&P methodologies, plus portfolio audit, zakat, dividend purification, market data, news and SEC filings, for Claude, Cursor, Windsurf and any MCP-compatible AI agent.",
"description": "Halal Terminal MCP server — 22 tools: screen stocks/ETFs across 5 Shariah methodologies (AAOIFI, DJIM, FTSE, MSCI, S&P), audit portfolios, calculate zakat and purification, fetch market data and SEC filings. For Claude, Cursor, Windsurf and any MCP client.",
Comment thread TOOLS.md
| `compare` | `run_id="id1,id2"` | Diff two runs |
| `list_indices` | — | Available indices |

Use when screening an entire index, filtering for compliant-only names, or comparing two screening runs. **Note: index runs consume many tokens — check `list_indices` and `summary` before triggering a full run.**
@goww7
goww7 merged commit ce9cb74 into main May 25, 2026
1 check passed
goww7 added a commit that referenced this pull request May 30, 2026
…imit)

PR #2 expanded the description to 239 chars, but the MCP registry caps it at 100
— that value cannot be republished. Restore the as-published value (96 chars),
reconciling the pre-existing local commit 47ac649; also ignore *.tgz.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants