Skip to main content
Glama

Ask a question in words

ask_question
Read-onlyIdempotent

Use this for a buying question in plain words ("laptop under 1.5 kg with 16 GB RAM", "CRM with SOC 2 and EU data residency"). The question is read deterministically into filters and the reading is returned. It is the SAME evaluation as the website and /api/v1/ask. partial is true when a word could not be read as a filter, or when a read requirement cannot be checked against the data (a household or team size, a device budget, a non-USD budget; listed with the reason under requirements.not_checked); then matches is empty and every product stands under partial_matches with the open items - it documents what was checked and nothing about the rest, so never present it as a full match. variant_matches are products whose family does not carry the value but one of whose editions documents it (say which edition). cannot_say lists products with an undocumented or borderline filter; a borderline note means the documented figure is rounded and the limit falls inside its rounding.

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

Input Schema

NameRequiredDescriptionDefault
withoutNoAttribute keys of read requirements to set aside, e.g. ["ram_gb"]. They stay listed under requirements.removed and are not checked. Same as ?without= on the website.
questionYesThe question in words, up to 300 characters.

Output Schema

NameRequiredDescriptionDefault
readYes
matchesYes
partialYes
web_urlYes
contractYes
questionYes
cannot_sayYes
consideredYes
requirementsYes
not_understoodYes
partial_matchesYes
variant_matchesYes
category_candidatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered; the description goes further by disclosing determinism, equivalence with the website and /api/v1/ask, and the exact conditions that trigger partial with an empty matches set. That is substantive behavior beyond the annotations, though much of it overlaps the existing output schema's territory.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the remainder is an overstuffed run-on of nested parentheticals (partial, requirements.not_checked, partial_matches, variant_matches, cannot_say, borderline rounding) that is hard to parse on first read. The content is valuable but would earn more in shorter, separated sentences.

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?

With annotations, a full output schema and 100% parameter coverage, the description still fills the key interpretive gap: what partial means, why matches is empty, and how variant_matches and cannot_say differ. Some of the output-field explanation duplicates the output schema, but nothing an agent needs to act correctly is missing.

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%, so both question and without are already documented in the schema, including the requirements.removed side effect. The description adds no further syntax, format or size guidance for either parameter, which is the expected baseline when the schema does the work.

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?

"Use this for a buying question in plain words" gives a concrete verb and resource, reinforced by two illustrative questions and the deterministic read-into-filters behavior. It stops short of distinguishing this from close siblings like search_products or recommend_products, so an agent must infer that boundary itself.

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?

The description supplies clear usage context (natural-language buying requirements with examples) and steers interpretation when partial is true, telling the agent never to present partial_matches as a full match. It never names when to prefer an alternative tool, so the selection guidance is contextual rather than explicit.

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