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 symbols over shared dates, each in its own unit, to reveal relative performance. Prices compare in percent, yields in percentage points; mixed types are flagged.

Instructions

Compare 2–6 symbols over shared observation dates, each in its own unit.

Example: ['BTC/USD', 'ETH/USD', 'SPY/USD'] or ['US2Y', 'US10Y']. Prices compare in percent,
yields in percentage points; mixed selections are flagged as not directly comparable.
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. Changed1 schema field changedv2.0.6
    • changedInput schema / properties / symbols / items / 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

A3.8/5.0
Behavior4/5

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

The annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds useful behavioral detail beyond that: shared observation dates, per-unit comparison, percent vs percentage-point treatment, and a warning flag for mixed selections.

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?

Three short sentences plus a compact example list carry the full meaning. Every sentence adds value, and the key scope is front-loaded before the examples and unit caveat.

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?

For a read-only comparison tool with an output schema, the description covers the essential calling decisions: symbol count, date mode, unit handling, and mixed-selection behavior. It could be more explicit about the relationship between period and start/end when both are provided, but the schema covers the mutual requirement.

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 only 50%; start and end have descriptions, while period and symbols rely on their enum/pattern constraints. The description compensates partly by giving symbol examples and explaining the start/end exact-window mode, but it does not fully define all parameter semantics.

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

Purpose4/5

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

The description states a specific verb ('Compare') and resource ('assets'), with a clear scope of 2–6 symbols over shared observation dates. It is unambiguous on its own, though it does not explicitly name sibling tools or differentiate from them.

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

Usage Guidelines3/5

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

Usage is implied: this is the tool for multi-symbol comparison, and the examples reinforce that. However, there is no explicit guidance on when to choose this over alternatives such as research_asset or market_overview, and no stated exclusions.

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