List all paid endpoints exposed by this MCP server with their prices and live status. Free — no wallet required. Use this first to discover what tools are available.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses the tool is free and requires no wallet, but lacks details on data freshness or completeness of the list.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with clear front-loading of purpose, then key info (free, no wallet), then usage guidance. No superfluous words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple zero-param tool. Covers purpose, cost, and usage order. Could mention whether the list is exhaustive or includes free endpoints.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Zero parameters with 100% schema coverage. Baseline is 4, and description adds no parameter info, which is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it lists paid endpoints with prices and live status. It explicitly positions itself as a discovery tool ('Use this first'), distinguishing it from sibling tools like pricing_info or install_snippets.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states 'Free — no wallet required' and 'Use this first to discover what tools are available,' giving clear when-to-use guidance and positioning it before other tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
list_endpoints and pricing_info overlap heavily—both surface pricing information, and an agent could easily pick the wrong one. The other three tools are more distinct, but this pair introduces real ambiguity.
The naming is readable but mixes styles: install_snippets and list_endpoints follow a verb_noun pattern, while pricing_info, usage_stats, and wallet_helper are noun-heavy labels. No chaotic mixing, but no strong consistent convention.
Five tools is a reasonable number for a small gateway server, and none feel entirely superfluous. There is minor redundancy between the two pricing-related tools, but the overall count is well-scoped.
The server describes itself as a gateway to paid endpoints, yet provides no tool to actually call any paid endpoint—only meta helpers for installation, discovery, pricing, usage, and wallet setup. This leaves agents unable to perform the server's core function.