Skip to main content
Glama

search_guides

Search Motozmo motorcycle repair guides and gear reviews by keyword to find relevant maintenance instructions and product insights.

Instructions

Search motozmo.com motorcycle repair guides and gear reviews by keyword.

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_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
queryYesSearch keywords, e.g. 'test motorcycle ground' or 'heated grips'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire burden, yet it says nothing about what a result contains (full guide text vs. snippets/links), whether matching is title-only or full-text, ordering/relevance, or whether requests are rate-limited. For a search tool with zero structured behavioral metadata, this leaves the agent guessing at the response shape.

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 the domain and scope stated immediately and no filler. It is efficient, though its brevity is partly the reason other dimensions are thin.

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?

For a simple two-parameter search tool with no output schema, the description establishes scope and domain adequately. It falls short on return-value expectations and on how results relate to the sibling retrieval tools, which an agent would need to choose confidently.

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 'query' documented via examples and 'limit' documented with bounds and default, so the structured data does the heavy lifting. The description adds only that the query is keyword-based, which is consistent with but not additive to the schema examples.

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 ('Search') and a concrete resource set ('motozmo.com motorcycle repair guides and gear reviews') qualified by 'by keyword'. It is clearly distinguishable from get_guide (single-item fetch) and the list_* siblings, though it does not name them 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?

The phrase 'by keyword' implies this is the tool for topical/term-based lookup rather than browsing latest or by topic, but the description never states when to prefer it over list_latest or list_topics, nor any exclusions or prerequisite conditions.

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

Deploy Server

Other Tools