Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add rules/0xchron/polymarket-mcp/mcp-tool-patternsgit clone --depth 1 https://github.com/0xChron/polymarket-mcpWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00513 |
| Opus 5 | $0.00000 | $0.00257 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
mcp-tool-patterns scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
MCP Tool Patterns
Adding a Tool
- Formatter in
utils/formatters.py— pure function, no I/O, returns markdown string - Tool in
tools/markets.pyortools/users.py—@mcp.tool()async handler that calls API and returnstext(formatter(data))
from polymarket_mcp.config import READ_ONLY_ANNOTATIONS, gamma_url
from polymarket_mcp.server import mcp
from polymarket_mcp.utils.helpers import get, text
from polymarket_mcp.utils.formatters import format_search_markets
@mcp.tool(annotations=READ_ONLY_ANNOTATIONS)
async def search_markets(query: str, limit: int = 5, active_only: bool = True):
"""Search Polymarket markets by title or description.
Returns matching markets with: current price, liquidity, volume,
end date, and active status."""
params = {"q": query, "limit_per_type": limit, "events_status": "active" if active_only else None}
data = await get(f"{gamma_url}/public-search", params=params)
return text(format_search_markets(data))
New tool modules must be imported from tools/__init__.py so registration runs at startup.
Tool Docstrings
- Become the agent-facing tool description — describe what is returned, not just parameters
- Use multi-line docstrings for complex tools
Response Format
- Formatters produce markdown (
#/##headers, key-value lines) - Always return via
text()— wraps markdown in JSON-encoded MCPTextContent - Errors:
err("message")for API failures; plain strings for input validation
Multi-API Tools
Use asyncio.gather(..., return_exceptions=True) and check each result:
portfolio_data, rank_data = await asyncio.gather(portfolio_task, rank_task, return_exceptions=True)
if isinstance(portfolio_data, Exception):
return err(str(portfolio_data))
API Selection
- Market discovery/details →
gamma_url(fromconfig.py) - User positions/portfolio/leaderboard →
data_url(fromconfig.py)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 57 lines · 0 tokens per session scan A d58f6e038922
mcp-tool-patterns is a cursor rule published in the GitHub repository 0xChron/polymarket-mcp (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 513 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other cursor rules, from other repositories
agoragentic-integrate
Connect an external agent host, framework, tool, or specialist engine to Agoragentic governance and receipts. Use for adapters, lifecycle mapping, MCP/tool discovery, and bounded integration design.
cursorrules
This repo has a GraphPilot structural code-graph available via MCP. Use it before grep on structural questions.
qa-agent
QA workflow for reviewing stories, designing tests, and reporting verified defects.
swift-development
Swift development: SwiftUI, Combine, async/await, iOS patterns, and Apple platform conventions.
clarify-first-prompting
Clarify-first strategy: detect ambiguity, ask targeted questions, expand simple prompts into detailed specifications.
cursorrules
When the user asks about social media, use social-media-ai-mcp tools: schedulepost, generatehashtags, analyzeengagement, plancontentcalendar, getaudienceinsights.