Skip to main content
Glama

MCP Foundry — Build, Test & Publish MCP Servers

search_servers

Search published public MCP servers in MCP Foundry

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_servers"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure and mostly fails it. It does not state whether results are paginated, ranked, truncated, or what fields are returned; only the 'published public' scope hints that private/unpublished servers are excluded.

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?

One tight sentence with the scope constraint front-loaded, which is appropriate for a simple lookup tool. It earns its place but leaves the reader wishing the same brevity had been spent on return-value and parameter behavior.

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

Completeness2/5

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

For a one-parameter discovery tool with no annotations and no output schema, the description should at minimum explain the search semantics and what the caller receives (e.g., server identifiers usable with get_server_tools). Neither is present, leaving the agent guessing at the contract.

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?

The single 'query' parameter has 0% schema description coverage and is not mentioned in the description at all — no indication of what it matches (name, description, tag), whether it is required, or what happens when it is omitted. The description adds no meaning beyond the bare property name.

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?

The description gives a specific verb ('Search') and a scoped resource ('published public MCP servers in MCP Foundry'), so an agent knows exactly what domain this touches. It stops short of explicitly contrasting with the sibling get_server_tools, which clearly operates on a single server rather than discovering them.

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 or when-not-to-use guidance, no mention of the sibling as a follow-up step, and no statement of prerequisites. The verb 'search' weakly implies a discovery use case, but the agent must infer that this is the entry point before calling get_server_tools.

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.