Skip to main content
Glama

Answer a data question

ask_anything
Read-onlyIdempotent

Takes a plain-language data question (official statistics, central bank rates, FX, energy, weather, holidays, research metadata). Every answer has an outcome. "answer": the value, only when the asked measure is word for word one known name of a series and its place, level and time fit and no other series fits as well; it carries answered_with (compare it with your question before you use it); a value history holds only the newest values, full true returns all of it. "candidates": otherwise, like find_data, up to 10 labelled series (publisher title, place with code and level, unit, latest value, range, source, licence) with the call_api arguments of each: choose the one whose measure, place and time match the question and pass its arguments to call_api (that second call returns the value); if none matches, tell the user this service does not have it. "none": nothing fits, with a reason. mode "candidates" always lists, mode "strict" gives the answer or none, never candidates. Examples: "population of pakistan", "unemployment rate california 2024". When to use: for any data question when you do not know the endpoint id. For a task with several figures or countries pass questions, not one call each. Use call_api instead when you already have an id, get_series for a long numeric history. Read-only, no API key or signup. Free quota: 1000 calls/day per IP, shared across tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ask_anything"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNooutcome answer: true returns the whole value history (default: only the newest values and those of the years asked for, see truncated).
modeNoauto (default): outcome answer when exactly one series is what is asked, otherwise candidates, otherwise none. candidates: always the candidates (or none). strict: answer or none, never candidates, for callers that cannot make a second call.
queryNoQuestion or keywords, max 200 characters
questionsNoSeveral questions answered in one call, in place of query. Split a task into one question per figure and place, e.g. ["inflation chile", "inflation peru"]. Each counts as one call of the quota.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / full / description
      Previous value: -"mode strict: true returns the whole value history (default: only the newest values and those of the years asked for, see truncated)."New value: +"outcome answer: true returns the whole value history (default: only the newest values and those of the years asked for, see truncated)."
    • changedInput schema / properties / mode / description
      Previous value: -"auto (default): candidates to choose from, no value on a guess. strict: one routed value or \"unfulfilled\", for callers that cannot make a second call."New value: +"auto (default): outcome answer when exactly one series is what is asked, otherwise candidates, otherwise none. candidates: always the candidates (or none). strict: answer or none, never candidates, for callers that cannot make a second call."
    • changedInput schema / properties / mode / enum
      Previous value: -[
      -  "auto",
      -  "strict"
      -]New value: +[
      +  "auto",
      +  "candidates",
      +  "strict"
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / full
      Added value: +{
      +  "description": "mode strict: true returns the whole value history (default: only the newest values and those of the years asked for, see truncated).",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / mode
      Added value: +{
      +  "description": "auto (default): candidates to choose from, no value on a guess. strict: one routed value or \"unfulfilled\", for callers that cannot make a second call.",
      +  "enum": [
      +    "auto",
      +    "strict"
      +  ],
      +  "type": "string"
      +}
  4. Changed2 schema fields changed
    • addedInput schema / properties / questions
      Added value: +{
      +  "description": "Several questions answered in one call, in place of query. Split a task into one question per figure and place, e.g. [\"inflation chile\", \"inflation peru\"]. Each counts as one call of the quota.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 10,
      +  "type": "array"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "query"
      -]
  5. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Natural language or keyword topic"New value: +"Question or keywords, max 200 characters"
  6. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint=false), it discloses the quota (1000 calls/day per IP, shared across tools), the absence of auth, the three-way outcome model (answer/candidates/none), and a real trust caveat — check answered_with against your question before using the value. Strict mode is explained as the path for callers that cannot make a second call, which is genuine behavioral context.

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?

It is front-loaded and dense — purpose, outcome model, mode semantics, examples, alternatives, quota — with almost no filler. The cost is a long run-on passage of quoted outcome names that reads more like compressed notes than clean prose, which slows parsing but does not waste sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so fully: it describes answer, candidates (including the per-candidate fields: publisher title, place with code and level, unit, latest value, range, source, licence, and the call_api arguments), and none with a reason. Quota, auth and fallback behavior for unmatched questions are all covered.

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%, so mode, full, query and questions are already documented, and the description largely restates them. It adds a little framing (candidates carry call_api arguments; questions each consume one quota unit), but no syntax, format or edge-case detail beyond the schema, so baseline 3 is right.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource — answer a plain-language data question over named domains (official statistics, central bank rates, FX, energy, weather, holidays, research metadata) — and immediately names the conditions that separate it from find_data, call_api and get_series, so an agent can route without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states explicit when-to-use ("any data question when you do not know the endpoint id"), explicit what-to-do-instead ("Use call_api instead when you already have an id, get_series for a long numeric history"), and batch guidance ("for a task with several figures or countries pass questions, not one call each").

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