Skip to main content
Glama
Alpha Sentinel Market Intelligence MCP

Alpha Sentinel Market Intelligence MCP

tokenized_stock_seal_receipt

Idempotent

Seals a Proof-of-Research receipt hash on Base, preparing unsigned calldata for ResearchReceiptRegistry and optional Sepolia submission to record research provenance.

Instructions

Seal a Proof-of-Research receipt hash on Base (ResearchReceiptRegistry).

Prepares unsigned calldata by default; optional Sepolia submit via env. Not trading.

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

Cost: $0.03 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": {
      "content_hash": "<content_hash>"
    },
    "name": "tokenized_stock_seal_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
brief_idNo
content_hashYes0x-prefixed SHA-256 of canonical brief JSON

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 openWorldHint and idempotent and non-destructive, and the description adds genuinely new operational facts: the default is an unsigned calldata preparation rather than a broadcast transaction, submitting to Sepolia requires an env flag, and each call costs $0.03 USD. The jurisdictional restriction (not offered to U.S. persons) is also behavioral context an agent cannot get from annotations. It stops short of saying what the returned calldata contains or whether a tx hash is produced.

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 core operation is front-loaded in the first sentence, followed by the default-mode caveat and the cost, which are the two facts most likely to change an agent's decision. The disclaimer and legal paragraph consume roughly a third of the text and contribute little to tool selection, though the U.S.-persons restriction is at least substantive.

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?

With no output schema, the description should say what the caller receives back — calldata plus target address, or a transaction receipt — and it only hints at 'unsigned calldata'. For a two-parameter, idempotent, cost-bearing write-preparation tool with annotated safety hints, this is adequate but leaves a real gap about the return payload and about brief_id.

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?

Only content_hash carries a schema description; brief_id has no description in the schema and is never mentioned in the prose, so half the parameters remain semantically opaque. The description does tie the hash to a canonical brief JSON indirectly, but does not explain the relationship between brief_id and content_hash or any format constraints.

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?

Names a specific verb (seal), a specific artifact (Proof-of-Research receipt hash), the chain (Base) and the contract (ResearchReceiptRegistry), which is far more precise than the sibling names suggest. It does not, however, explicitly differentiate itself from tokenized_stock_research_brief, which is presumably the producer of the hash.

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 description implies the usage context (sealing a research receipt) and clarifies that the default mode produces calldata rather than broadcasting, with an optional Sepolia submit gated by env. It never states when an agent should seal versus just call the research brief tool, nor any prerequisite ordering, leaving the trigger condition to inference.

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