Skip to main content
Glama

Get a number's value on a date

get_value_on
Read-only

What a number was on a given past day, from the record: the last value on or before that day, the date it was recorded, what set it when known (for example a funding round), its source, and when it next changed. Nothing is interpolated. Use it for questions like 'what was X's valuation in March 2025'.

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": {
      "date": "<date>"
    },
    "name": "get_value_on"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe number's id, from search_numbers.
dateYesThe day to look up, YYYY-MM-DD.
pageNoOr the number's page address on tallycatalog.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses the exact retrieval semantics: last value on or before the date, the recording date, the causal context when known, the source, and the next change date. The explicit 'nothing is interpolated' statement is a meaningful behavioral constraint an agent would otherwise have to guess.

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?

Front-loads the return shape, then the interpolation caveat, then the example question — a logical order with no filler. The first sentence is long and list-heavy but every clause maps to a real output field.

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 no output schema, the description usefully substitutes by enumerating returned fields, and the id-from-search_numbers hint lives in the schema. Minor gaps remain: it doesn't say what happens when no value exists on or before the date, or how id and page interact if both are given.

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 id, date format, and the page alternative are already documented; the description adds only the implicit mapping of 'the number' to the id. Baseline 3 applies when the schema carries the parameter burden.

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 pair: resolving a number's value on a given past day, and enumerates exactly what comes back (value, recorded date, what set it, source, next change). An agent can distinguish it from a plain metadata lookup like get_number, though it doesn't name any sibling explicitly.

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 triggering use case ('what was X's valuation in March 2025') and the 'Nothing is interpolated' note implicitly warns against expecting derived trends. No explicit when-not-to-use or named alternative (e.g. get_history) is provided.

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.