Skip to main content
Glama
nomina-xyz

Nomina

Official
by nomina-xyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Research an asset

research_asset
Read-onlyIdempotent

Retrieve a symbol's latest value, period change, drawdown, volatility, dated history, and headlines for market research.

Instructions

Research one symbol: latest value, period change, drawdown/volatility, dated history, headlines.

Symbols: on-chain feeds like BTC/USD, ETH/USD, SPY/USD, EUR/USD, XAU/USD (BTC, btc-usd,
BTCUSD also work); Treasury yields US1M..US30Y (e.g. US10Y); macro CPI, UNRATE, PAYEMS,
AHE. Daily observations, weekly beyond two years, monthly for macro series. 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. Changed1 schema field changedv2.0.6
    • changedInput schema / properties / symbol / pattern
      Previous value: -"^[A-Za-z0-9^=._-]+$"New value: +"^[A-Za-z0-9/:._-]+$"
  2. 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"
+}
  3. First observedv1.0.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: data frequency changes by horizon, symbol aliases are accepted, and start/end require each other. It doesn't mention pagination or rate limits, but for a read-only research tool with rich annotations, this is strong.

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?

The description is compact and front-loaded: the first sentence states the tool's purpose and outputs, the second covers symbol formats, and the third covers data frequency and window usage. Every sentence earns its place; no filler or repetition of schema fields.

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

Completeness5/5

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

For a read-only research tool with an output schema, the description covers the essential invocation details: what data comes back, which symbols are valid, how frequency changes, and how to request a custom window. The output schema handles return-value documentation, and annotations handle safety. Nothing critical is missing for an agent to call this correctly.

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 50%: symbol has no description in the schema, while start/end/period have basic descriptions. The description compensates by explaining symbol formats and aliases, period semantics (daily/weekly/monthly), and the start/end window behavior. It doesn't detail every enum value, but the enum is self-documenting and the description clarifies the key ambiguity around date windows.

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?

The description opens with a specific verb ('Research') and resource ('one symbol'), then enumerates the exact data points returned: latest value, period change, drawdown/volatility, dated history, headlines. It also lists supported symbol families (on-chain feeds, Treasury yields, macro series), which distinguishes it from siblings like search_markets or compare_assets. This is a clear, specific statement of what the tool does.

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

Usage Guidelines5/5

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

The description gives explicit usage context: it handles one symbol at a time, lists accepted symbol formats and aliases, explains data frequency (daily, weekly beyond two years, monthly for macro), and tells the agent to provide start/end for an exact window instead of period. This effectively routes the agent away from siblings like compare_assets (multi-asset) and search_markets (discovery).

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

Deploy Server

Other Tools