Skip to main content
Glama

Perceptlayer

Call a data endpoint

call_endpoint
Read-only

Run one endpoint and return its JSON response. Spends the call's credits from the user's balance on success only; failed calls are free. Pass parameters exactly as get_endpoint lists them (array parameters as JSON arrays). The result reports credits used and remaining. Errors come back with a code: invalid_parameters (fix the parameters and retry), not_found (no data for these parameters), rate_limited or temporarily_unavailable (wait and retry), insufficient_credits, restricted_endpoint (the user must accept the restricted-endpoint terms in their dashboard), invalid_api_key (the MCP server config needs a valid API key). Responses over 100,000 characters are truncated; use paging or limit parameters to fetch less.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "endpoint": "<endpoint>"
    },
    "name": "call_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsNoParameters for the endpoint, e.g. {"listing_id": "18648717"}.
endpointYesEndpoint ID from search_endpoints, e.g. "airbnb.listing".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: it discloses that credits are charged only on success, that the response reports credits used and remaining, that responses over 100,000 characters are truncated, and how restricted endpoints must be unlocked. The credit-spend disclosure is exactly the kind of side effect the annotations do not capture, and it is stated plainly.

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?

Five sentences, each load-bearing: what it does first, then cost model, then parameter format, then error handling, then truncation limits. No restatement of the title or schema, and the most decision-relevant facts are front-loaded.

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?

There is no output schema, yet the description characterizes the return value (JSON plus credit accounting), names every recoverable error class with a remedy, and warns about the truncation ceiling. For a two-parameter proxy tool with a free-form params object, nothing an agent needs before calling is missing.

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?

With 100% schema coverage the baseline is 3, but the description adds real meaning: parameters must be passed exactly as get_endpoint lists them, and array parameters must be JSON arrays — a non-obvious serialization rule for a free-form object parameter. It also points to paging/limit parameters as the remedy for truncation.

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?

States a specific verb and resource ('Run one endpoint and return its JSON response') and implicitly distinguishes itself from the sibling get_endpoint by telling the caller to take parameter shapes from it. An agent can tell this is the execution tool versus the discovery/introspection tools without opening a schema.

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?

Gives clear operational context: parameters come from get_endpoint, failed calls cost nothing, and each error code maps to a next action (fix and retry, wait and retry, accept terms in dashboard, fix server config). It stops short of an explicit 'use this instead of X when Y' statement, but the workflow dependency on get_endpoint is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources