USERDATA

pull_prices

Fetches daily Yahoo Finance prices for a ticker and chosen period, then stores them for traceable market data research.

Instructions

Stores daily prices for a Yahoo period such as "1y" or "max".

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": {
      "ticker": "<ticker>",
      "period": "<period>"
    },
    "name": "pull_prices"
  }
}

Input Schema

Name	Required	Description	Default
`period`	Yes
`ticker`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 8, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, yet "Stores" hints at a write or persistence side effect without saying what is stored, where, whether it overwrites existing data, or whether a network request to Yahoo is involved. It says nothing about error behavior for invalid tickers or rate limits. The existence of an output schema excuses it from describing return values, but the mutation/IO semantics remain ambiguous.

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 sentence with no filler or redundancy. It is arguably too terse rather than overly verbose, and the period example is placed usefully at the end.

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 two-parameter tool with zero schema coverage and no annotations, the description leaves critical gaps: what ticker format is expected, and whether "stores" means the call mutates state. The presence of an output schema covers return-value description, but the input and side-effect semantics are incomplete.

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 description coverage is 0%, so the description must compensate for both parameters. It partially does so for period by giving concrete examples ("1y", "max"), but ticker receives no format guidance at all (e.g., symbol casing, exchange suffixes), leaving half the parameters undocumented in both schema and description.

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 names a resource ("daily prices") and a scoping concept ("a Yahoo period"), but the verb "Stores" conflicts with the tool name pull_prices, leaving it unclear whether the tool fetches data, persists it, or both. It also never mentions the ticker parameter, which is the primary identifier, so the agent must infer that this is a per-ticker price retrieval tool.

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?

There is no guidance on when to use this tool versus siblings such as query_market, pull_company, or pull_filings, nor any prerequisites or exclusions. The only usage-relevant information is an implicit hint about valid period formats, which the agent must extract from a parenthetical example.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.