Skip to main content
Glama

Nova Amazon MCP Server

describe_metric

Read-only

Get the full definition of a single metric (meaning, unit, grains it is valid at; for a Vendor Central (1P) metric, its basis; for a memo line beside the P&L, its group; for a Subscribe & Save metric, readingNote: how it reads over a period and when a day of it is final).

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": {
      "key": "<key>"
    },
    "name": "describe_metric"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesA metric key from list_metrics, e.g. "netSales" — or a natural name that means exactly one metric (tacos, avgPrice…).
reasonNoOne sentence, ALWAYS IN ENGLISH (regardless of the conversation language), on WHY you are making this call — the user question or your analytical goal. Recorded so the seller can see how their data is used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this a safe, closed-world read, so no credit is due for that. What the description adds beyond them is genuinely domain-specific: it discloses that certain returned fields are conditional on the metric family (1P basis, memo-line group, Subscribe & Save readingNote with its over-a-period and day-finality semantics), which is real behavioral knowledge an agent could not infer from annotations. It stops short of saying what happens with an ambiguous or unknown key, which the schema hints is possible.

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?

A single front-loaded sentence that opens with the core action before layering on the conditional return fields; nothing is redundant. It is dense with nested parentheticals, though, and a short second clause on the key requirement would cost little and read more cleanly.

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?

There is no output schema, so the description carries the return-value burden and does so by naming the conditional fields per metric family rather than leaving the response shape opaque. For a two-parameter read tool with full annotation coverage this is close to complete; only the failure/ambiguity behavior for `key` is unaddressed.

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% and both parameters are documented there, including the natural-name acceptance for `key` and the always-in-English `reason` convention. The description adds no parameter guidance of its own, so the baseline 3 applies — the schema is doing all of that work.

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?

"Get the full definition of a single metric" states a specific verb and resource and scopes it to one metric, which cleanly separates it from the bulk sibling tools list_metrics and query_metrics. The parenthetical then enumerates exactly which definitional attributes come back (meaning, unit, valid grains, and the conditional `basis`/`group`/`readingNote`), so an agent knows the payload without opening anything else.

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: the phrase "full definition" signals this is the lookup to reach for when a metric's meaning or unit is unclear, and the per-family field hints suggest calling it before interpreting a Vendor Central, memo-line, or Subscribe & Save metric. The description never states when to prefer it over list_metrics or query_metrics, gives no precondition (the key must come from list_metrics), and no exclusions.

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.