Skip to main content
Glama

path_answer

Read-onlyIdempotent

A read of the data (a total, an average, a count, the top group), computed on every row, in this response. When the question is not a read it says so and names the next step. Time: as path_resolver quotes.

No key yet? Call it with objective and data (a small table, up to 200 rows): a read of that table comes back now, nothing stored. Sign-in is needed to save, re-run, or ask for more than a read.

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": {
      "objective": "<objective>"
    },
    "name": "path_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoWITHOUT A KEY: up to 200 rows pasted inline as flat objects, e.g. [{"month":"Jan","sales":120}]. Use instead of dataset_ref.
objectiveYesthe question, in the person's words
dataset_refNothe dataset: the `usage` value from datasets_list (uuid://ID or uuid://ID:KEY), or its id, for a dataset the caller owns or the platform sample
resolution_idNoThe resolution_id from path_resolver's path_input. Pass path_input as given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / data
      Added value: +{
      +  "description": "WITHOUT A KEY: up to 200 rows pasted inline as flat objects, e.g. [{\"month\":\"Jan\",\"sales\":120}]. Use instead of dataset_ref.",
      +  "items": {
      +    "type": "object"
      +  },
      +  "maxItems": 200,
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "objective",
      -  "dataset_ref"
      -]New value: +[
      +  "objective"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / dataset_ref / description
      Previous value: -"the dataset: a uuid://, upload:// or dataset id the caller owns"New value: +"the dataset: the `usage` value from datasets_list (uuid://ID or uuid://ID:KEY), or its id, for a dataset the caller owns or the platform sample"
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds value the annotations cannot: the call is free, computation happens on every row of the supplied data, nothing is stored on the keyless path, and the tool abstains rather than guessing. Missing only deeper cost/latency or limit behavior beyond 'as path_resolver quotes'.

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

Conciseness5/5

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

Front-loads the operation and its return semantics in the first sentence, then handles the keyless case and the sign-in boundary. Telegraphic style ('Time: as path_resolver quotes') is terse but each sentence carries a distinct calling constraint.

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?

No output schema, yet the description says what comes back (a total, average, count, top group) and that non-reads return a pointer to the next step. Auth requirements and the keyless path are covered; what's thin is what the abstention payload looks like and how resolution_id interacts with the other two data parameters.

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

Parameters4/5

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

Schema coverage is 100%, so 3 is the baseline, but the description adds real meaning: data is the keyless alternative to dataset_ref with a 200-row cap, and objective doubles as both the question and the keyless invocation payload. The resolution_id-to-path_input relationship is left entirely to the schema.

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 operation (compute a total/average/count/top group over every row) and that the result is returned in this response, which separates it from the planning siblings (path_resolver, path_estimate) and the re-run tool. The phrasing 'a read of the data' and 'when the question is not a read' is jargon-y shorthand, so an agent must infer that 'read' means aggregation, but the core purpose is recoverable.

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?

Gives two concrete entry conditions: if the question is not a read, the tool abstains and names the next step; with no key, call it with objective plus an inline data table. It also flags that sign-in is required to save, re-run, or go beyond a read, which implicitly routes to the re-run/auth-gated siblings. It does not name those siblings explicitly, so routing still relies on inference.

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.