Skip to main content
Glama

Search Quo's travel Q&A library

search_answers
Read-onlyIdempotent

Search Quo's library of real, specific Florida travel answers, airport transfers, getting around, event logistics, itineraries by city. Returns matching question/answer pairs.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesA question or topic, e.g. 'Art Basel traffic' or 'Miami airport transfer'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the return shape (matching question/answer pairs), but says nothing about result ranking, empty-result behavior, or the limit cap of 10.

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?

Two tight sentences with the content scope front-loaded and the return value last. Every clause carries information, though 'real, specific' is mild marketing filler.

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 simple two-parameter read tool with full annotations and a stated return shape, the definition is mostly sufficient. The only real omission is any mention of how the limit parameter behaves or what happens when nothing matches.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: query is documented in the schema, but limit has no description anywhere. The description never mentions a result count, pagination, or a maximum, so it fails to compensate for the undocumented parameter.

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+resource ('Search Quo's library of ... Florida travel answers') and even names the domains covered (airport transfers, getting around, event logistics, itineraries). It is clear what the tool retrieves, though it never explicitly contrasts itself with the obvious sibling ask_concierge.

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?

No when-to-use guidance beyond the topic list; nothing says when to search the library versus asking ask_concierge or consulting get_city_guide. The agent must infer the choice from names alone.

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