Skip to main content
Glama
entroute

EntRoute MCP

Official

discover_paid_api

Find pay-per-request APIs for any capability using natural language. Returns ranked, verified endpoints with pricing, success rate, and latency. Input your intent or capability ID, set filters like max price or network, and get reliable options before calling.

Instructions

Discover pay-per-request API endpoints for a given capability.

Returns ranked, verified endpoints with pricing and reliability metrics. Use this to find APIs before calling them. The results include:

  • Endpoint URL and method

  • Price per call and payment network

  • Success rate and latency metrics

  • Provider information

After discovering, you can use call_paid_api to execute the endpoint.

Trust & safety:

  • "Verified" means the endpoint returns a valid x402 402 response -- it does not guarantee the quality or accuracy of the data returned after payment.

  • Endpoints are probed every 10 minutes. Check last_verified and success_rate to gauge reliability.

  • Fallback endpoints (unverified) have failed recent verification checks -- use with caution.

  • Prefer endpoints with success_rate >95% and verification within the last 24 hours.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intentYesNatural language description of what you want to do (e.g., "get current weather for London", "translate text to Spanish"). Provide this or capability_id.
capability_idNoExplicit capability ID if known (e.g., "weather.current", "translate.text"). Alternative to intent for precise matching.
max_priceNoMaximum price per request in USD (e.g., 0.01 for 1 cent)
networkNoRequired blockchain network for payment
ranking_presetNoRanking preference preset
limitNoMaximum number of endpoints to return (default: 5)
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, description fully discloses behavioral traits: verification meaning ('x402 402 response', not data accuracy), probing frequency (10 minutes), reliability guidance (prefer >95%, <24h), and fallback endpoint caution. Exceeds expectations for transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise and well-structured: brief summary, bulleted results list, clear trust & safety section. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 6 parameters with 100% schema coverage and no output schema, the description is complete: explains purpose, usage, safety, and ranking guidance. No gaps for an agent to execute correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and descriptions are clear, but the description adds context: 'natural language description' for intent, 'precise matching' for capability_id, and explicit pricing and ranking defaults. The description adds moderate value beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it discovers pay-per-request API endpoints for a given capability, with specific verb ('discover') and resource ('paid API endpoints'). It distinguishes itself from sibling tools like 'call_paid_api' (which executes) and 'list_capabilities' (which lists capabilities).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this to find APIs before calling them' and directs to 'call_paid_api' for execution. Provides when-to-use context and alternative/next step.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/entroute/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server