Skip to main content
Glama

Search providers

search_providers
Read-onlyIdempotent

Search technology providers by name, category and city.

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": {
      "q": "<q>"
    },
    "name": "search_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch words, such as a provider name or service, for example "managed kubernetes".
limitNoNumber of results to return. Default 8, maximum 20.
categoryNoExact primary category to filter by, as listed by list_categories.
locationNoCity to filter by, as listed by list_categories with facet location_city.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Exact primary category to filter by, as listed by list_categories."
    • addedInput schema / properties / limit / description
      Added value: +"Number of results to return. Default 8, maximum 20."
    • addedInput schema / properties / location / description
      Added value: +"City to filter by, as listed by list_categories with facet location_city."
    • addedInput schema / properties / q / description
      Added value: +"Search words, such as a provider name or service, for example \"managed kubernetes\"."
  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 readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond that: no note on result ordering, matching semantics (substring vs. token), what happens when q matches nothing, or how paging works for an open-world search. It restates the name and filters rather than supplying behavioral context.

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 short sentence, front-loaded with verb and resource, with no filler or repetition. It is efficient, though its brevity contributes to the guidance gaps noted elsewhere rather than being a flaw of structure itself.

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?

All four parameters are fully documented and the annotations are rich, so the minimum an agent needs to call the tool is present. What is missing is anything on result behavior for an open-world search or on choosing this tool over the other search siblings, which matters given the crowded sibling set.

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 100%, with each of the four parameters documented, including defaults and max for limit and the list_categories dependency for category and location. The description only echoes those same three facets and never mentions limit or the required q behavior, so it adds no meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

"Search technology providers by name, category and city" gives a specific verb (search) and resource (technology providers) plus the three filter dimensions. It is clear what the tool does, but it does nothing to distinguish it from siblings like "search", "similar_providers", or "search_content", so an agent must infer which search entry point applies.

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, and no alternative is named despite several sibling tools that also search. The only routing hints (that category and location values come from list_categories) live in the schema, not the description, so the description itself leaves selection entirely to inference.

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