Skip to main content
Glama
Sign In
traivo-mcp

traivo-mcp

Official
by traivoxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Stock token board

get_stock_board
Read-onlyIdempotent

Returns live on-chain prices for tokenized Ethereum stocks, including bid, ask, mid, spread, and premium versus the listed share price, with optional symbol filtering.

Instructions

Live board of tokenized stocks on Ethereum mainnet (Ondo Global Markets tokens, traded on Uniswap V3 against USDC). Per token: on-chain bid (USDC for selling 1 token), ask (USDC per token when buying with $1,000), mid, spread, the listed share's last price as the reference with its age in seconds, and the premium of the on-chain mid vs that share price in bps. Also returns ethUsd, the ETH price. Null prices mean the pool is not quoted; a null reference means there is no listed share to compare against. The tokens trade around the clock but the share price only moves while its exchange is open, so a large referenceAgeSec outside US market hours is normal.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_stock_board"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsNoOnly return these symbols. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the description's real contribution is the quoting model: the ask price assumes a $1,000 buy, the bid assumes selling 1 token, and null prices mean the pool is unquoted. It also explains why referenceAgeSec can legitimately be large, which prevents an agent from misreading the data as stale. Missing are any notes on refresh cadence, rate limits, or latency.

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?

It is front-loaded with the one-sentence summary, then returns, then null semantics, then the market-hours caveat — a logical progression with no filler. The field enumeration is dense but every clause carries signal; only the parenthetical Ondo/Uniswap detail is borderline verbose.

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?

With no output schema, the description carries the full burden of explaining return values and does so thoroughly, including the meaning of nulls, the units of each metric, and the ETH price field. An agent can interpret every field without additional documentation.

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 description coverage is 100%, and the single optional `symbols` filter is fully documented in the schema, including ticker examples and case-insensitivity. The description adds no further meaning about the filter (e.g., behavior when a symbol is unknown or not listed), so baseline 3 applies.

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 names a specific resource and scope: a live board of tokenized stocks (Ondo Global Markets tokens) on Ethereum mainnet, traded on Uniswap V3 against USDC. It then enumerates exactly what each row contains (bid, ask, mid, spread, reference price, referenceAgeSec, premium in bps, ethUsd), which cleanly separates it from siblings like get_crypto_markets and get_onchain_tokens.

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 (fetch a market snapshot for stock tokens) but there is no explicit when-to-use or when-not-to-use language, and no sibling is named as an alternative. The note about large referenceAgeSec outside US market hours is interpretive guidance for the output rather than invocation guidance.

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