Skip to main content
Glama

search_services

Read-onlyIdempotent

Use when a customer asks about gate types, repairs or borough coverage. Returns matching page titles, descriptions and canonical 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": {
      "query": "<query>"
    },
    "name": "search_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesGate type, repair need or NYC borough, such as emergency rolling gate repair in Queens.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds some value by disclosing what comes back (titles, descriptions, canonical URLs), which matters since there is no output schema. It says nothing about result count limits, relevance ranking, or what happens when nothing matches.

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 sentences, zero filler, with the usage trigger front-loaded ahead of the return description. Every sentence carries information an agent needs.

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

Completeness4/5

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

For a one-parameter read-only search tool with full schema coverage and safety annotations, this is nearly complete: trigger condition and return shape are both stated even though no output schema exists. The only real gap is result-set behavior (how many matches, ranking, empty-result handling).

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% and the single query parameter already has a detailed description with an example ('emergency rolling gate repair in Queens') plus length bounds. The description only restates the topical categories already implied by the schema, so it adds no syntax or formatting guidance beyond structured fields. 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?

The description names the resource being searched (site/page content about gate types, repairs, borough coverage) and states the return payload as page titles, descriptions and canonical URLs, which lets an agent infer it is a site-content search tool. It stops short of explicitly saying 'searches the website pages', and doesn't contrast with the sibling get_quote_guide.

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

Usage Guidelines4/5

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

It gives an explicit trigger: 'Use when a customer asks about gate types, repairs or borough coverage.' That is clear when-to-use context. There is no when-not condition and no named alternative for queries outside those topics (e.g., pricing, which is plausibly what get_quote_guide covers), so routing to siblings is left 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