Skip to main content
Glama
nomina-xyz

Nomina

Official
by nomina-xyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Compare assets

compare_assets
Read-onlyIdempotent

Compare 2–6 asset symbols on aligned dates in their local currencies. Get period returns, actual dates, source URLs, and adjustment basis—no FX conversion or trading advice.

Instructions

Compare 2–6 distinct symbols over aligned observation dates in their local currencies.

Example: ['NVDA', 'AMD', 'SPY']. Includes period returns, actual dates, source URLs,
adjustment basis and individual failures. No FX conversion or trading advice.
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
symbolsYes

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.5/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, and open-world behavior. The description adds valuable behavioral context beyond those annotations: aligned observation dates, local currencies, inclusion of period returns, actual dates, source URLs, adjustment basis, and individual failures. This gives the agent a strong sense of what the tool returns and its limitations.

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 core purpose, followed by an example, output contents, limitations, and parameter guidance. Every sentence earns its place without redundancy.

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 tool with an output schema and rich annotations, the description covers the essential user-facing behavior: symbol count, period vs. exact-date selection, output contents, and explicit non-goals. An agent has enough information to select and invoke the tool correctly.

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 50%: start and end are documented in the schema, while symbols and period rely on types/enums. The description adds useful context by stating the 2–6 symbol range and advising start/end for an exact window instead of a period. It does not fully compensate for the period parameter semantics, but the enum values are largely self-explanatory.

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 starts with a specific verb and resource: 'Compare 2–6 distinct symbols over aligned observation dates in their local currencies.' This clearly identifies what the tool does and distinguishes it from sibling tools like search_markets or market_overview. The example symbols further reinforce the intended use case.

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?

The description clearly implies the tool is for multi-asset comparisons and explicitly excludes FX conversion and trading advice. It also gives clear directional guidance on choosing an exact start/end window instead of a preset period. However, it does not explicitly name alternative tools or state when not to use this tool in favor of a sibling.

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