Skip to main content
Glama

alpha-sentinel-mcp

tokenized_stock_corporate_action

Fetch one announced/applied corporate action by UUID (from onchain Announcement URI).

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

Cost: $0.02 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": {
      "corporate_action_id": "<corporate_action_id>"
    },
    "name": "tokenized_stock_corporate_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
corporate_action_idYesUUID from Announcement event URI

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 genuinely useful non-schema context: a $0.02 per-call cost, a research-only scope, and explicit exclusion of trading/execution/custody/swaps. It does not disclose auth requirements, behavior for an unknown or malformed UUID, or what statuses "announced/applied" cover in the payload.

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 sentence, followed by scope disclaimers and cost in a scannable order. The compliance block is boilerplate but plausibly required, so it earns its place though it dilutes focus from invocation details.

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 one-parameter read tool with no output schema and no annotations, the description covers purpose, cost, and legal scope but leaves the caller guessing about return payload contents and failure modes. Those omissions are the main reason this is adequate rather than complete.

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 schema coverage is 100% with the schema itself describing it as a "UUID from Announcement event URI." The description restates that origin without adding format examples or validity constraints, so it neither helps nor hurts beyond the schema baseline.

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?

"Fetch one announced/applied corporate action by UUID" gives a specific verb (fetch), a specific resource (corporate action), and a cardinality constraint (one) plus the key type (UUID), which distinguishes it from list/lookup-style siblings. It stops short of naming a sibling or stating the boundary explicitly, so it lands just below the top.

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 phrase "from onchain Announcement URI" implies the caller already holds an announcement reference, which is implied usage guidance. However, there is no statement of when to prefer this over a list/lookup call, nor what to do when only a symbol or date is known.

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.