Skip to main content
Glama

alpha-sentinel-mcp

tokenized_stock_lookup

Lookup metadata for one tokenized stock (contract, ISIN, multiplier, prospectus).

RESEARCH ONLY — not investment advice. No trading, execution, custody, or swaps. Coinbase tokenized stocks are not offered to U.S. persons.

Cost: $0.01 USD per call

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": "tokenized_stock_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesToken ticker e.g. CRCLc

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does add real value — read-only metadata lookup, a $0.01 per-call cost, and explicit compliance restrictions — but says nothing about failure behavior for an unknown ticker, whether results are cached/stale, or what the response looks like.

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?

Purpose is front-loaded in the first sentence, with the compliance constraints and cost in short, scannable blocks. Every line carries information an agent or caller needs; nothing is redundant padding.

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 single-parameter lookup with no output schema, the description usefully enumerates the principal returned fields and states the cost, which is enough to call it correctly. The remaining gap is error/edge-case behavior on an invalid or unknown symbol.

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?

Only one parameter, and the schema documents it fully ("Token ticker e.g. CRCLc", non-empty). The description adds nothing about ticker format, case sensitivity, or lookup behavior beyond the schema, so this lands at the 100%-coverage baseline of 3.

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?

States a specific verb and resource ("Lookup metadata for one tokenized stock") and names the concrete fields returned (contract, ISIN, multiplier, prospectus). The singular "one" implicitly contrasts with the plural list tool, but no sibling is named explicitly, so it stops just short of full sibling differentiation.

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 block gives clear scope context: research only, no trading/execution/custody/swaps, and a U.S. persons restriction. That is explicit when-to-use and when-not-to-use framing, though it never routes the agent to an alternative for related needs (e.g., listing, corporate actions) and gives no prerequisite guidance.

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.