Skip to main content
Glama

Similar providers

similar_providers
Read-onlyIdempotent

Find providers similar to a directory listing.

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": {
      "slug": "<slug>"
    },
    "name": "similar_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesURL slug of the record, as returned by a search tool, for example "acme-cloud".
limitNoNumber of similar providers to return. Default 6, maximum 12.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Number of similar providers to return. Default 6, maximum 12."
    • addedInput schema / properties / slug / description
      Added value: +"URL slug of the record, as returned by a search tool, for example \"acme-cloud\"."
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds only that similarity is measured against 'a directory listing', which barely elaborates the title — it says nothing about how similarity is determined, whether results exclude the source provider, or whether it works on listed-but-unverified records.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though efficiency here comes at the cost of detail rather than because the detail was unnecessary.

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?

The tool is simple (2 params, full schema coverage, rich annotations, no output schema), so little is strictly required. However, the core semantic of 'similar' — likely same-category/related-listing recommendations — is undefined, and an agent cannot tell what a returned set represents.

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 coverage is 100%: slug's format and example, plus the limit default of 6 and max of 12, are all documented in the schema. The description adds no meaning beyond that, so the baseline 3 applies.

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 ('providers similar to a directory listing'), which is enough to distinguish it from get_provider (fetch one) and search_providers (query by criteria). It does not explicitly name those siblings, so it falls short of a 5.

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 guidance on when to choose this over search_providers or get_provider, no prerequisites (does the slug need to exist?), and no mention of what the result is useful for. The agent must infer the use case entirely from the tool 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