Skip to main content
Glama
Alpha Sentinel Market Intelligence MCP

Alpha Sentinel Market Intelligence MCP

tokenized_stock_corporate_action

Read-onlyIdempotent

Retrieve a specific announced or applied tokenized-stock corporate action by UUID from its onchain Announcement URI for research and event tracking.

Instructions

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

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive behavior, so the safety profile is covered. The description adds material context beyond that: a per-call cost of $0.02 USD and a compliance constraint ('not offered to U.S. persons'), both of which affect whether an agent should call it. It does not disclose the shape of the returned action, which is the remaining gap.

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?

Three short blocks, front-loaded with the action and keyed parameter, then the research disclaimer and cost. The disclaimer is boilerplate but plausibly necessary for a tokenized-equity tool; nothing is padding beyond that.

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 one-parameter, read-only, idempotent lookup with no output schema, the description gives the agent enough to invoke it correctly: what it retrieves, the key to supply, the cost, and the usage restrictions. Only the return contents and error behavior for an unknown UUID are left unstated.

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?

Schema coverage is 100% and the single parameter is already documented as 'UUID from Announcement event URI'. The description restates the same provenance rather than adding new format or validity constraints, so the baseline of 3 for fully covered schemas applies.

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 leads with a specific verb and resource: 'Fetch one announced/applied corporate action by UUID'. The word 'one' plus the UUID keying distinguishes it from a list-style sibling such as tokenized_stock_list, even though no sibling is named explicitly.

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?

It states the input prerequisite — the UUID comes 'from onchain Announcement URI' — which implies when the tool is usable. However, there is no explicit when-to-use/when-not guidance and no named alternative for cases where the caller does not already hold an announcement UUID.

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