Skip to main content
Glama

mocop

search_apis

Read-only

Search REST/GraphQL APIs.

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": {
      "query": "<query>"
    },
    "name": "search_apis"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesNatural language or keyword query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety and locality profile is covered without help from the description. The description adds no behavioral context beyond them — nothing about result ranking, default/maximum result count, or what happens when the query is empty or matches nothing.

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

Conciseness3/5

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

A single five-word sentence is efficient with no padding, but at this length the terseness crosses into under-specification rather than disciplined conciseness. Nothing is front-loaded because there is essentially nothing to load.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should ideally indicate what a result contains (API names, endpoints, descriptions) and how many are returned. For a two-parameter read-only search, the annotations plus schema cover the basics, but the tool's output shape and the effect of 'limit' stay unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

Schema coverage is only 50%: 'query' is documented in the schema, but 'limit' (1-25) has no description anywhere, and the description supplies no parameter meaning at all. It does not clarify whether the query supports natural language vs keyword syntax differences beyond the schema's brief note, so the low coverage is left uncompensated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Search') and a resource type ('REST/GraphQL APIs'), which loosely separates it from the sibling searches for agents, capabilities, and MCP servers. However, it never says what corpus is being searched — the user's own domains, a public catalog, or an internal registry — so the scope remains vague.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no statement of when this tool is preferable to search_agents, search_capabilities, or search_mcp_servers, and no note that it is the entry point for later calls like get_entity or analyze_site. The agent must infer applicability purely from the name.

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