Skip to main content
Glama
Sign In

MCP Heartbeat

by com.mcpheartbeat
OverviewDiscussionsAdmin

Find tools

find_tools
Read-onlyIdempotent

Find servers whose measured tools match a capability. Results are grouped by server and include page URLs.

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": {
      "capability": "<capability>"
    },
    "name": "find_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
capabilityYesWords matched against tool name and description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / capability / pattern
      Added value: +"\\S"
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds genuine value by disclosing the result shape: grouped by server, with page URLs. It omits ranking/ordering, whether matching is any-word or all-word, and how 'limit' affects the grouping, which would matter for open-world search.

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?

Two short sentences with no filler, and the core purpose is front-loaded before the result-shape detail. Every clause carries information an agent can act on.

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?

With no output schema, the description usefully sketches the return shape (grouped by server, page URLs), which partially covers the gap. However, for a search tool with an undocumented 'limit' parameter and no stated matching logic, the definition is only adequate rather than complete.

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%: 'capability' is documented in the schema as words matched against tool name and description, but 'limit' has no description beyond min/max bounds. The description does not clarify what limit counts (servers, groups, or results per server) or how capability words combine. It therefore fails to compensate for the coverage gap.

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 and resource combination: find servers whose measured tools match a capability. The phrase 'measured tools' plus 'grouped by server' makes clear this is a capability-based server discovery tool, distinct from a name-based server lookup. It stops short of naming a sibling to contrast against, so an agent must infer the boundary with search_servers.

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

Usage Guidelines3/5

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

Usage is only implied: you use it when you have a capability in mind and want matching servers. There is no explicit statement of when to prefer this over search_servers, no prerequisites, and no exclusions. An agent can guess the intent but gets no routing guidance.

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

All MCP Heartbeat toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources