Skip to main content
Glama

EntRoute

by com.entroute

discover_paid_api

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

  • sample_request / sample_response: Example request body and response showing the exact parameter names and format the endpoint expects. ALWAYS use sample_request as your template when calling the endpoint — do not guess parameter names.

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
limitNoMaximum number of endpoints to return (default: 5)
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.
networkNoRequired blockchain network for payment
max_priceNoMaximum price per request in USD (e.g., 0.01 for 1 cent)
capability_idNoExplicit capability ID if known (e.g., "weather.current", "translate.text"). Alternative to intent for precise matching.
ranking_presetNoRanking preference preset

TDQS

A4.6/5.0
Behavior5/5

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

No annotations provided, so the description carries full burden. It discloses that 'Verified' means a valid 402 response, not data quality. Mentions probing every 10 minutes, last_verified, success_rate, fallback endpoints, and the importance of using sample_request as a template.

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

Conciseness4/5

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

Well-structured with bullet points and clear sections. Front-loaded with purpose. Slightly lengthy but each sentence adds value. Could be slightly more concise, but overall effective.

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, no output schema, and no annotations, the description is highly complete. It covers tool purpose, return structure, parameter guidance, trust/safety info, and usage flow. No significant gaps.

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 description coverage is 100%, baseline is 3. The description adds extra context: explains sample_request/response usage, describes 'intent' as natural language description, and provides guidance on parameter usage. Adds meaningful 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 'Discover pay-per-request API endpoints for a given capability' and lists what it returns (URL, method, pricing, reliability, provider, sample_request/response). It distinguishes itself from sibling tools 'call_paid_api' (execution) and 'list_capabilities' (listing capabilities).

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

Usage Guidelines4/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 mentions using 'call_paid_api' after discovery. Provides guidance on preferring endpoints with high success rates and recent verification. No explicit exclusion of alternatives, but the context is clear.

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

All EntRoute toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool targets a distinct action: listing capabilities, discovering endpoints for a capability, and calling a discovered endpoint. No overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (list_capabilities, discover_paid_api, call_paid_api), making the set easy to navigate.

Tool Count5/5

Three tools is well-scoped for the server's purpose of discovering and calling paid APIs. Each tool serves a necessary step in the workflow.

Completeness4/5

The core workflow (list capabilities, discover endpoints, call endpoints) is covered. Minor missing features like checking payment status or endpoint details without discovery are not critical given the design.

Resources