Free Live Data MCP

search_endpoints

Read-onlyIdempotent

Find API operations by task or discover lookup and autocomplete endpoints when an entity ID is needed. Search local metadata across the catalog without using API quota.

Instructions

Find operations within an API or across the catalog. Search for the task or for lookup/autocomplete operations when an entity ID is required. Discovery uses local metadata and no API 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_endpoints"
  }
}

Input Schema

Name	Required	Description	Default
`apiId`	No
`limit`	No
`query`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Oct 29, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive behavior, so those need no restating. The description adds genuinely new context the annotations lack: discovery runs on local metadata and consumes no API quota, which matters for agents deciding whether to probe freely.

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?

Three short sentences, front-loaded with the resource and scope, then usage intent, then the cost characteristic. No filler and no restatement of the tool name or schema.

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?

For a three-parameter search tool with no output schema and no parameter descriptions, the agent still lacks pagination/limit behavior and any hint of what results look like (endpoint names, methods, paths). The quota note is valuable, but the definition leaves gaps an agent would want filled before calling.

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 0% for all three parameters, so the description must carry the load. It does explain apiId implicitly (within an API vs across the catalog) and what query should contain (task descriptions or lookup/autocomplete operations), but says nothing about the limit parameter or its 30-item cap.

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

Purpose4/5

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

States a specific verb (find) and resource (operations/endpoints) with its scope: within one API via apiId or across the whole catalog. An agent can distinguish it from search_apis by the resource type searched, though the description never names that sibling, so differentiation relies partly on the name.

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?

"Search for the task or for lookup/autocomplete operations when an entity ID is required" gives a concrete usage condition rather than leaving intent implicit. However, it never states when NOT to use it or points to describe_endpoint/call_endpoint as the follow-on alternatives.

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

Deploy Server