Skip to main content
Glama
nomina-xyz

Nomina

Official
by nomina-xyz

Research an asset

research_asset
Read-onlyIdempotent

Retrieve dated prices, performance, and news links for one Yahoo Finance symbol by providing its ticker plus a period or start/end dates, returning source URLs and data limitations.

Instructions

Research one Yahoo Finance symbol with dated prices, performance, history and news links.

Examples: AAPL, SPY, ^GSPC, BTC-USD, EURUSD=X, GC=F. Discover unfamiliar symbols
with search_markets first. Includes source URLs and data limitations, not financial
statements or full articles. History uses daily bars, or weekly bars for five years.
Give start and end (YYYY-MM-DD) for an exact window instead of period.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoISO date, inclusive; requires start.
startNoISO date, inclusive; requires end.
periodNo3mo
symbolYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • addedInput schema / properties / end
      Added value: +{
      +  "anyOf": [
      +    {
      +      "format": "date",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "ISO date, inclusive; requires start.",
      +  "title": "End"
      +}
    • addedInput schema / properties / start
      Added value: +{
      +  "anyOf": [
      +    {
      +      "format": "date",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "ISO date, inclusive; requires end.",
      +  "title": "Start"
      +}
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds useful context: content boundaries ('source URLs and data limitations, not financial statements or full articles') and data granularity ('daily bars, or weekly bars for five years'). No contradiction with annotations.

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?

Four sentences, purpose first, with no filler. Examples, usage guidance, data limitations, and parameter advice are packed into a compact, scannable block that earns each sentence.

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 an output schema present and a modest parameter count, the description covers symbol format, date/period alternatives, data scope, and a search hint. Minor omissions like the 3mo default and the required flag are already handled by the schema, so nothing critical is missing.

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?

With only 50% schema coverage, the description compensates by giving concrete symbol format examples and explaining that start/end replace period for exact windows. It clarifies date format (YYYY-MM-DD) and that the two dates are used together, though it doesn't enumerate period values except the five-year behavior.

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?

Description opens with 'Research one Yahoo Finance symbol with dated prices, performance, history and news links' – a specific verb and resource. The singular 'one symbol' scope and examples distinguish it from compare_assets and market_overview, while naming search_markets for discovery.

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 explicit guidance: use search_markets first for unfamiliar symbols, and use start/end for exact windows instead of period. It doesn't explicitly contrast when to prefer compare_assets or market_overview, but the 'one symbol' framing provides implied context.

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