Skip to main content
Glama

Call an endpoint

call_api
Read-onlyIdempotent

Runs one endpoint by id with parameters and returns its data as compact JSON (source, license, data_freshness included). Bundles answer whole tasks in one call: bundle-location-brief (weather, time, holidays for a place), bundle-country-brief, bundle-eurozone-brief, bundle-energy-brief-de, bundle-npm-package-brief. When to use: you know the endpoint id (from search_apis, from alternatives or catalog_choices of ask_anything, or from the docs) and want to set parameters exactly, e.g. another country or date. params are the endpoint's own query parameters as listed by search_apis (example_query). Unknown ids or bad params return an error message naming the problem. Read-only, no API key or signup. Free quota: 1000 calls/day per IP, shared across tools.

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": {
      "apiId": "<apiId>"
    },
    "name": "call_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoReturn the whole answer even above about 2,500 tokens (default false: long lists are shortened)
apiIdYesEndpoint id, e.g. fx-currency-convert or bundle-location-brief
fieldsNoOptional comma-separated data fields to return (dot paths), saves tokens
paramsNoQuery parameters as key-value map, e.g. {"from":"USD","to":"EUR","amount":"250"}
verboseNoInclude full provenance metadata (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / full
      Added value: +{
      +  "description": "Return the whole answer even above about 2,500 tokens (default false: long lists are shortened)",
      +  "type": "boolean"
      +}
  2. Changed3 schema fields changed
    • changedInput schema / properties / apiId / description
      Previous value: -"The API ID e.g. bundle-location-brief, fx-currency-convert"New value: +"Endpoint id, e.g. fx-currency-convert or bundle-location-brief"
    • changedInput schema / properties / fields / description
      Previous value: -"Optional comma-separated data fields to return (dot paths)"New value: +"Optional comma-separated data fields to return (dot paths), saves tokens"
    • changedInput schema / properties / params / description
      Previous value: -"Query parameters key-value map"New value: +"Query parameters as key-value map, e.g. {\"from\":\"USD\",\"to\":\"EUR\",\"amount\":\"250\"}"
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Well beyond the annotations, it discloses truncation behavior (~2,500 token default, full=true overrides), provenance fields included in the response, error behavior for unknown ids or bad params, no API key required, and a 1000 calls/day per IP quota shared across tools. These are exactly the operational traits an agent needs before calling.

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?

Front-loaded with purpose and return shape, then bundles, then when-to-use, then failure modes and quota. Every sentence carries information, though the enumeration of five bundle ids adds bulk that could be summarized.

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?

For a 5-parameter tool with nested params and no output schema, the description covers invocation intent, return shape and truncation, error handling, auth, and rate limits. Nothing an agent needs to call it correctly 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?

Schema coverage is 100%, so the baseline is 3; the description adds value by explaining that `params` are the endpoint's own query parameters as published in search_apis' example_query, which the schema only vaguely calls a 'key-value map'. It does not further explain `fields` dot-path syntax or `verbose` beyond the schema, so not a 5.

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 ('Runs one endpoint by id') plus the return format ('compact JSON with source, license, data_freshness'). It also names the bundle endpoints it covers and its sibling sources (search_apis, ask_anything), so an agent can distinguish it from get_series/get_history 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 Guidelines5/5

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

Explicit 'When to use' clause: you already know the endpoint id (from search_apis, from alternatives/catalog_choices of ask_anything, or the docs) and want exact parameter control. That routes the agent away from discovery tools and toward exact invocation, with a concrete example ('another country or date').

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