Skip to main content
Glama

alpha-sentinel-mcp

tokenized_stock_list

List Coinbase tokenized stocks on Base (read-only catalog).

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

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional name/symbol/ISIN filter
page_sizeNo
page_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does meaningfully well: it declares the operation read-only, states a per-call cost of $0.01 USD, and discloses a legal/geographic restriction on U.S. persons. It is silent on pagination behavior and the shape of the returned catalog entries, which are the remaining behavioral gaps.

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?

The definition is tightly front-loaded: purpose first, then constraints, then cost. Every line is short and scannable, and the compliance and cost statements are genuinely load-bearing rather than filler. Minor redundancy between 'read-only' and 'No trading, execution, custody' keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description could have explained what a catalog entry contains, and with 33% schema coverage it should have covered the paging parameters; neither is addressed. What it does cover — read-only nature, cost, and eligibility restrictions — is solid, but an agent still lacks enough to page results or interpret entries confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — 'query' is documented but 'page_size' and 'page_token' carry no descriptions beyond a default and min/max. The description adds no parameter-level meaning at all; it never mentions filtering by name/symbol/ISIN nor how to page through the catalog, so it fails to compensate for the coverage gap.

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 gives a specific verb and resource combination ('List Coinbase tokenized stocks on Base') plus scope ('read-only catalog'), so an agent knows exactly what the tool returns at a high level. It does not differentiate itself from the sibling tokenized_stock_lookup, which is plausibly adjacent in function, so it stops short of a 5.

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?

The 'RESEARCH ONLY' framing and the prohibition list (no trading, execution, custody, swaps) establish clear usage boundaries and a compliance condition (not offered to U.S. persons). However, there is no guidance on when to prefer this catalog listing over tokenized_stock_lookup or the other tokenized_stock_* siblings, so routing is left to inference.

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.