gblin-treasury-risk-regime

actions.status

Read-onlyIdempotent

Report what a sent Base transaction did: pending, succeeded, reverted or not found; its block and confirmations; the fee paid; the net token movements for the sender (GBLIN shares minted or redeemed, USDC, basket tokens); and, when it reverted, the decoded reason. Use it after sending the steps from prepare_action to confirm each one before the next.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`hash`	Yes	The transaction hash.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`to`	No
`from`	No
`hash`	Yes
`note`	No
`block`	No
`revert`	No
`status`	Yes
`fee_eth`	No
`explorer`	No
`gas_used`	No
`gas_limit`	No
`confirmations`	No
`balance_changes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 23, 2026
- changedOutput schema / properties / confirmations / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```
AddedSep 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Even with annotations already declaring readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, the description adds substantial behavioral detail: it reports statuses, block and confirmations, fee, net token movements, and decoded revert reasons. This goes well beyond the annotations and informs the agent what kind of output to expect.

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

Conciseness5/5

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

The description is information-dense but not bloated. It front-loads the core purpose, then lists the key reported fields, and closes with a clear usage instruction. Every clause contributes useful detail for tool selection and invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a single well-documented parameter, an output schema, and annotations covering safety, the description provides sufficient context: when to call it, what it reports, and how it fits into the prepare_action workflow. Nothing essential is missing.

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 description coverage is 100% and the only parameter, hash, is already described as 'The transaction hash.' The description confirms it refers to a sent Base transaction but does not add meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Report') and resource ('what a sent Base transaction did'), then enumerates concrete outcomes: pending, succeeded, reverted, or not found. This distinguishes it from sibling tools like actions.prepare and actions.preview, which clearly operate at different stages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells the agent when to use this tool: 'after sending the steps from prepare_action to confirm each one before the next.' This is clear contextual guidance, though it does not name alternative tools or explicitly state when not to use it.

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

All gblin-treasury-risk-regime tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.