Skip to main content
Glama

marketplace.search

Read-only

Search active public MCP server metadata by name and description.

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": "marketplace.search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesRequired full-text search query.
categoryNoOptional exact category/tag.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's main added value is the 'active public' filtering constraint. It says nothing about result ordering/relevance, whether results are paginated, or what happens when nothing matches — behavior an agent would need to interpret output.

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?

A single front-loaded sentence with no filler; the verb, scope, and matching fields all appear before any trailing detail.

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 three parameters, no output schema, and no annotations beyond readOnlyHint, the description should say more about what 'metadata' is returned and how limit/pagination behaves. It is adequate to call the tool but leaves the agent guessing about result shape and result-count semantics.

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?

The phrase 'by name and description' meaningfully explains which fields the required query string matches against, adding value beyond the schema's generic 'Required full-text search query'. However, the optional category and limit parameters get no treatment in the description, and at 67% schema coverage the schema carries most of the remaining weight.

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 well-scoped resource ('active public MCP server metadata'), and clarifies that matching happens against name and description. It is clear what the tool does, though it makes no attempt to differentiate itself from the listed sibling tools (which appear to be unrelated catalog/whoami utilities).

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?

The word 'active' and 'public' implicitly exclude inactive or private servers, which is useful scoping, but there is no explicit when-to-use versus when-not-to-use guidance and no mention of alternatives. An agent can infer the use case but must guess at the boundaries.

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