Skip to main content
Glama
Alpha Sentinel Market Intelligence MCP

Alpha Sentinel Market Intelligence MCP

tokenized_stock_lookup

Read-onlyIdempotent

Retrieve metadata for a tokenized stock by ticker, including contract address, ISIN, multiplier, and prospectus link, so you can verify asset details for research.

Instructions

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 observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, yet the description adds genuinely new context: a per-call cost of $0.01 USD, a research-only restriction with no trading/custody/swaps, and a jurisdictional eligibility limit. That is substantive behavioral and compliance information not present in 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.

Conciseness5/5

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

Roughly sixty words with the purpose front-loaded, then scope, then cost in a bolded line. Every sentence carries distinct information—the disclaimer and cost are not filler.

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?

With no output schema, the description usefully enumerates the metadata fields returned, and it covers scope, cost, and eligibility for a single-parameter read tool. Minor gaps remain: no mention of behavior for an unknown symbol or whether tickers are case-sensitive.

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?

There is only one parameter and schema coverage is 100%, with the schema itself explaining the ticker format ('e.g. CRCLc'), so the baseline is 3. The description's field list describes return contents rather than adding meaning to the 'symbol' argument.

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 names a specific verb and resource ('Lookup metadata for one tokenized stock') and enumerates the returned fields (contract, ISIN, multiplier, prospectus). The singular 'one tokenized stock' implicitly contrasts with the plural sibling tokenized_stock_list, though no sibling is named outright.

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 only implied: the agent can infer this is for single-symbol metadata lookup rather than listing or corporate actions. The description adds a real eligibility constraint ('not offered to U.S. persons') and a research-only scope, but never states when to prefer a sibling tool over this one.

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