Skip to main content
Glama

EntRoute

by com.entroute

call_paid_api

Call a previously discovered API endpoint.

Use this after discover_paid_api to execute the request.

IMPORTANT: You must first use discover_paid_api to find an endpoint. Then use the endpoint_id from the discovery result. Use the sample_request from the discovery result as your body template — it shows the exact parameter names the endpoint expects. Replace the example values with the actual values you need.

Payment: this hosted server holds no wallet, so it cannot settle x402 payments. Free endpoints return their data directly. Paid endpoints return the payment challenge (amount, recipient, network) without charging anything. To pay automatically, run the local server instead: npx @entroute/mcp-server with EVM_PRIVATE_KEY set.

Trust & safety:

  • EntRoute verifies that endpoints return valid 402 responses every 10 minutes, but does not guarantee response quality or accuracy. Treat results like any third-party API.

  • Prefer endpoints with high success rates (>95%) and recent verification timestamps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoRequest body (for POST/PUT/PATCH)
methodNoHTTP method (defaults to endpoint method)
headersNoAdditional headers to include in the request
endpoint_idYesThe endpoint_id from a previous discover_paid_api result
query_paramsNoQuery parameters to append to URL

TDQS

A4.8/5.0
Behavior5/5

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

No annotations provided, so the description bears full responsibility. It discloses that the hosted server cannot settle payments, describes the behavior for free vs paid endpoints, and details the trust & safety aspects (verification intervals, success rate recommendations). This goes well beyond the schema and provides essential behavioral context.

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?

The description is thorough but well-structured with clear sections (IMPORTANT, Payment, Trust & safety). It front-loads the core purpose and prerequisite. Some redundancy exists (e.g., repeated mention of discover_paid_api), but overall it is concise for the amount of context needed.

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 the tool's complexity (5 parameters, workflow dependency, payment handling), the description covers all necessary aspects: prerequisite tool, how to construct the request, payment behavior, and safety guidelines. No output schema exists, but the description appropriately focuses on input and behavior.

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% with basic descriptions for each parameter. The description adds significant workflow context: explains how endpoint_id relates to discover_paid_api, and mentions using sample_request as a body template. This enhances understanding beyond the schema, though it does not add per-parameter details.

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 the tool's action: 'Call a previously discovered API endpoint.' It specifies the prerequisite (use after discover_paid_api) and distinguishes from the sibling discover_paid_api, which handles discovery. The verb 'call' and resource 'API endpoint' are specific and unambiguous.

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 states when to use: after discover_paid_api. Provides step-by-step guidance: use endpoint_id and sample_request from discovery. Explains payment scenarios (free vs paid) and recommends the local server for automatic payment. No explicit 'when not to use', but the context is sufficiently clear to avoid misuse.

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