Skip to main content
Glama

Asset

asset
Read-onlyIdempotent

Use when someone asks about one coin or stock: why $X is moving, whether its volume is unusual, how its past spikes turned out, or where it trades. One asset in depth: latest snapshot, scores_30d (30 days of readings, the newest of each UTC hour), the open event and the 10 most recent past events with score_at_open, peak_score and receipts, and venues: where it trades (spot, perpetuals, futures, prediction markets), plain unpaid links checked nightly against each venue's product list. latest.score is the newest Activity score, the same number as the last point of scores_30d. When no event is open, driver is null and reason is no open event: a driver is read from the open event. Same data as GET /api/asset/{symbol}, plus score on latest and that reason. heat_7d (the same readings, each ts and heat) and peak_heat are deprecated aliases of scores_30d and peak_score, same values, kept until at least 2026-12-31.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker symbol, e.g. BTC or GME

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantial context beyond them: the freshness of venue links ('plain unpaid links checked nightly against each venue's product list'), the null-driver behavior when no event is open ('reason is no open event'), and the equivalence of latest.score to the final point of scores_30d. The deprecation contract for heat_7d/peak_heat with a concrete sunset date is exactly the kind of forward-compatibility detail an agent cannot get from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the usage scenario, which is good, but the body is a dense run-on chain of clauses with repeated restatements (the latest.score / last-point-of-scores_30d equivalence is said twice in effect). The deprecated-alias housekeeping and the API-endpoint mapping ('Same data as GET /api/asset/{symbol}') consume space that a calling agent rarely needs, though they do earn some place as versioning notes.

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 takes on the burden of explaining return fields and does so thoroughly: scores_30d granularity ('newest of each UTC hour'), event fields (score_at_open, peak_score, receipts), venues, and the no-open-event edge case. An agent can interpret the response without further discovery.

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?

The single symbol parameter is fully documented in the schema ('Ticker symbol, e.g. BTC or GME'), so the schema carries the load. The description only reinforces it indirectly via '$X' and 'one coin or stock', adding no format, case-sensitivity, or resolution rules beyond the schema. Baseline 3 applies at 100% coverage.

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 precise resource and scope: 'One asset in depth' with an enumerated payload (latest snapshot, scores_30d, open event, past events, venues), which is clearly narrower than aggregate tools like board, get_index or arena. It never names a sibling to contrast with, but the 'one coin or stock' framing makes the unit of retrieval unambiguous.

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?

It gives explicit trigger conditions tied to real user questions: 'why $X is moving, whether its volume is unusual, how its past spikes turned out, or where it trades.' That is a clear when-to-use signal. There is no when-not guidance and no named alternative for multi-asset or market-wide questions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources