Skip to main content
Glama

Primary Source Commodities

Resolve Observation

observation.resolve
Read-onlyIdempotent

Resolve a single observation by its id. Derived observations (crack, crush, basis) cite the observations they were computed from in inputs[]; this is how you dereference those ids to audit a derived value. Ids look like obs_<24 hex>.

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": {
      "id": "<id>"
    },
    "name": "observation.resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesObservation id, e.g. from a derived observation's inputs[] array.

Output Schema

NameRequiredDescriptionDefault
idNoStable observation id
citeNoOne-line citation for agents
nameYesHuman-readable instrument name
unitYesUnit of measure
as_ofYesAs-of date for the observation
priorNoPrevious print value when history exists
valueYesObserved numeric value
inputsNoInput series ids when derived
sourceYesPrimary source provenance
derivedYesTrue when value is derived
formulaNoDerivation formula when derived
qualityYesData quality label
raw_hashNoHash of raw source payload
series_idYesUnderlying series id
instrumentYesInstrument code, e.g. CL
pct_changeNoPercent change vs prior print
provenanceYesRetrieval / cache provenance
license_tagYesLicense / redistribution tag
observed_atYesISO timestamp when observed
short_historyNoNewest-first short history (≤8 points)
freshness_classYesFreshness class for the series

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and repeatability are covered. The description adds context the annotations don't: the id format (obs_<24 hex>) and the provenance/audit semantics of resolving inputs[] references. It doesn't cover behavior on an unknown or malformed id, and with an output schema present the return shape needn't be described.

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?

Three tight sentences, front-loaded with the core operation and then immediately with the non-obvious dereference use case. No repetition of the title, no filler, and every clause adds new information (derived types, inputs[], id format).

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?

For a single-parameter read tool with full annotation coverage and an output schema, the description supplies what an agent needs: what it resolves, where ids come from, and the id format. The only minor gap is not saying what happens for an unknown id or whether non-derived observations also have inputs[].

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 description coverage is 100% and the single id parameter is documented, so the baseline would be 3. The description earns above baseline by adding the concrete id format ('obs_<24 hex>') and, more importantly, where ids come from (a derived observation's inputs[] array), which is semantic context the schema only hints at.

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 verb and resource ('Resolve a single observation by its id') and goes beyond a bare restatement by explaining that derived observations (crack, crush, basis) cite their source observations in inputs[], so this tool is the dereference step. That distinguishes it meaningfully from the sibling *.get tools, which are generic getters. It stops short of naming an alternative for the non-derived case, but the purpose is unambiguous.

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 a concrete when-to-use trigger: when you have ids from a derived observation's inputs[] and need to audit the derived value. That is real workflow guidance rather than an implied use. It does not state exclusions (e.g., when a plain getter should be used instead), which keeps it below a 5.

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