Skip to main content
Glama

Search the endpoint catalog

search_apis
Read-onlyIdempotent

Searches the catalog of verified endpoints (official statistics, interest rates, FX, energy, weather, geo, holidays, research, developer tools) by keyword and returns the best matches (10 by default) with id, short description, parameter names and an example query. When to use: to browse what exists for a topic, or when ask_anything returned "unfulfilled" or a low-confidence match. Pass the chosen id to call_api. Does not fetch any data and does not count against the quota.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_apis"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of matches, 1-30 (default 10)
searchNoKeywords, e.g. "electricity price germany"
categoryNoOptional category filter, e.g. "Finance"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Number of matches, 1-30 (default 10)",
      +  "type": "number"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / category
      Added value: +{
      +  "description": "Optional category filter, e.g. \"Finance\"",
      +  "type": "string"
      +}
    • changedInput schema / properties / search / description
      Previous value: -"Optional keyword search"New value: +"Keywords, e.g. \"electricity price germany\""
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses that no data is fetched and that the call does not count against the quota, plus the shape of the response (id, description, parameter names, example query). These are operational facts the annotations cannot express.

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 key identity and the 'When to use' guidance are front-loaded and the category list is informative rather than padding. It is one dense paragraph though, so the router/usage/return information would scan faster as separated sentences.

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 read-only discovery tool with no output schema, the description supplies purpose, invocation conditions, return contents, quota impact, and the next step in the workflow. 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.

Parameters3/5

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

Schema description coverage is 100% and all three parameters are documented there, so the schema does the heavy lifting. The description reinforces keyword search and the default of 10 matches but adds no syntax, category naming rules, or limit behavior beyond the 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?

Specific verb+resource ('searches the catalog of verified endpoints') with an enumerated category scope, and it clearly separates itself from siblings by stating it only discovers ids while call_api fetches data and ask_anything handles question answering.

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 covers browsing for a topic and the failure case of ask_anything returning 'unfulfilled' or low confidence, and it names the follow-up action ('Pass the chosen id to call_api'). A concrete alternative and its trigger condition are given.

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