Skip to main content
Glama

Ask the Quo concierge

ask_concierge

Ask a natural-language question and get a grounded answer from Quo's own concierge, the same AI that answers the site's chat widget. Strictly grounded in real Quo information; never invents a price or a policy.

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": {
      "question": "<question>"
    },
    "name": "ask_concierge"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The description adds a genuine behavioral guarantee beyond the annotations — answers are 'strictly grounded in real Quo information' and never invent prices or policies. However, with readOnlyHint=false and openWorldHint=true declared, an agent might expect the description to explain what side effect occurs or why the call is not read-only; that is left unexplained, as are latency and any rate limits.

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 compact sentences, front-loaded with the action and followed by the grounding guarantee. The 'never invents a price or a policy' clause is slightly redundant with 'strictly grounded' but earns its place as concrete reassurance.

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 single-parameter tool with no output schema, the description covers intent and trustworthiness but says nothing about what comes back — whether the answer includes sources, links, or citations — which an agent needs to plan follow-up steps.

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 0% for the single `question` parameter, so the description must carry the load. It does convey that input is a natural-language question about Quo, but it never mentions the 2–500 character bounds or any phrasing guidance, so it only partially compensates.

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 a specific verb+resource ('Ask a natural-language question and get a grounded answer from Quo's own concierge') and characterizes the answering engine as the site chat widget's AI. It does not, however, differentiate itself from the sibling search_answers, leaving the agent to guess which Q&A surface to pick.

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?

Usage is only implied: an agent can infer this is for free-form natural-language questions about Quo. There is no explicit when-to-use, no when-not-to-use, and no reference to any alternative tool such as search_answers, get_membership_info, or get_fleet.

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