Skip to main content
Glama
Alpha Sentinel Market Intelligence MCP

Alpha Sentinel Market Intelligence MCP

tokenized_stock_list

Read-onlyIdempotent

Retrieve a read-only catalog of Coinbase tokenized stocks on Base, with optional filters by name, symbol, or ISIN and pagination for browsing results.

Instructions

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

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds two things annotations cannot: a concrete per-call cost of $0.01 USD and an eligibility constraint (not offered to U.S. persons), both of which materially affect whether an agent should invoke it. It stops short of describing pagination behavior or the shape of returned records.

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?

Purpose is front-loaded in the first line, followed by scope limits and cost — a sensible ordering with little wasted text. The compliance disclaimer block is somewhat boilerplate but short enough to earn its place as a usage constraint.

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?

For a three-parameter, zero-required listing tool with no output schema, the definition covers purpose, safety, cost and eligibility, which is most of what an agent needs. The missing pieces are pagination semantics and any hint about returned fields, which matter for a catalog endpoint where an agent may need to page through results.

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 bounds. The description says nothing about filtering syntax, pagination mechanics, or how page_token should be sourced, 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 names a specific verb and resource — 'List Coinbase tokenized stocks on Base' — and labels it a 'read-only catalog', which is far more than a restatement of the tool name. It does not, however, explicitly distinguish itself from tokenized_stock_lookup, so the agent must infer that this is the browse-all endpoint rather than the single-item lookup.

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 by 'read-only catalog' and by the negative framing 'No trading, execution, custody, or swaps', which rules out use cases this tool does not serve. There is no explicit statement of when to call this versus tokenized_stock_lookup or the other tokenized_stock_* siblings, and no prerequisite guidance beyond the U.S. persons restriction.

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