Skip to main content
Glama

AI Capital Index

get_price_history

Every dated price record and recorded price change. Requires a Pro, Team or Institutional key.

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": "get_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoYYYY-MM-DD
modelNo
providerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description bears the full behavioral burden and supplies only the key-tier requirement. It says nothing about pagination, ordering, date-range defaults, whether the full history is returned or truncated, or what a 'recorded price change' entry looks like.

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?

Two short, front-loaded sentences with no filler. The brevity is efficient, though the opening sentence is a fragment that reads as a restatement of the title rather than a lead-in to action.

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

Completeness2/5

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

For a tool with three optional, partly undocumented parameters, no annotations, and no output schema, the definition leaves too much open: return shape, default date range, and the meaning of the model/provider filters are all unstated.

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

Parameters2/5

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

Schema coverage is 33%: only 'from' is documented in the schema (YYYY-MM-DD), while 'model' and 'provider' have no description anywhere. The description adds no detail on these parameters, so it fails to compensate for the low coverage.

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

Purpose3/5

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

The description is a noun phrase ("Every dated price record and recorded price change") rather than a verb+resource statement, so the agent must infer that it retrieves historical price data from the name alone. It does convey scope (all dated records plus changes), but gives no signal distinguishing it from the sibling get_model_prices.

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

Usage Guidelines2/5

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

The only conditional statement is an access prerequisite ("Requires a Pro, Team or Institutional key"). There is no indication of when to prefer this over get_model_prices or get_ai_funding_rounds, and no exclusions or scenario context.

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