Skip to main content
Glama

Suggest search terms

suggest
Read-only

Autocompletes partial or uncertain search terms, returning query and subcategory matches so users can recover when a search yields no useful results.

Instructions

Autocomplete for a partial or uncertain search term: returns suggested queries and matching subcategory names. Use when a search returns nothing useful.

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": "suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesPartial or uncertain term, e.g. "hallo".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and externality are covered structurally. The description adds value by disclosing the return shape (suggested queries and subcategory names), but says nothing about result limits, ranking, or empty-result behavior.

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 core behavior front-loaded and the usage trigger second. Nothing could be removed without losing meaning.

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 lookup with no output schema, the description supplies the missing piece: what comes back (suggested queries and subcategory names). Only minor gaps remain around result volume and how suggestions relate to actual search tools.

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 parameter is documented with an example ("hallo"), so the schema does the heavy lifting. The description's "partial or uncertain term" reinforces intent but adds no format or constraint detail beyond the schema.

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 and resource: "Autocomplete for a partial or uncertain search term" plus what it returns (suggested queries and matching subcategory names). This clearly separates it from search_products, though no sibling is named explicitly.

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?

"Use when a search returns nothing useful" gives a concrete trigger condition, which is real guidance. It stops short of naming alternatives or stating when-not to use it (e.g. when a term is already exact), so the agent must infer the fallback relationship.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.