Skip to main content
Glama

alpha-sentinel-mcp

tokenized_stock_seal_receipt

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 observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description does real work: it discloses that nothing is submitted on-chain by default, that Sepolia submission is env-gated, that it is non-trading/non-custodial, and that each call costs $0.03. Still missing key behavior: idempotency if a hash is re-sealed, which chain/registry contract address, and what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and well-segmented with a bolded cost line, but the trading disclaimer is stated twice back-to-back ("Not trading" then "No trading, execution, custody, or swaps"), and the U.S. persons note consumes space without aiding invocation.

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?

No output schema and no annotations, so the description should describe the returned calldata structure and any submit-mode return value; it only alludes to "unsigned calldata." For a two-parameter write-path tool it is adequate but leaves the return contract underspecified.

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?

At 50% schema coverage, the schema documents content_hash (0x-prefixed SHA-256 of canonical brief JSON) but not brief_id. The description adds no meaning about brief_id's role or how it relates to the sealed receipt, so it only partially compensates 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?

States a specific verb ("Seal") and resource ("Proof-of-Research receipt hash on Base (ResearchReceiptRegistry)"), which clearly separates it from sibling research/listing tools. It does not explicitly name a sibling alternative, but the action is unambiguous.

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?

"Prepares unsigned calldata by default; optional Sepolia submit via env" gives meaningful mode context, and the "RESEARCH ONLY" framing implies it belongs after generating a research brief. However, it never states when to seal versus skip, nor which sibling produces the input hash.

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.