explain_approvalExplain an arbitrary approval/permission JSON payload in plain language, when you already have the data instead of needing an on-chain lookup.
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | Arbitrary approval/permission JSON payload to explain |
| Name | Required | Description | Default |
|---|---|---|---|
| verdict | Yes | SAFE, CAUTION or RISK | |
| explanation | Yes | Plain-language explanation of what the approval or payload allows |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": {},
+ "properties": {
+ "explanation": {
+ "description": "Plain-language explanation of what the approval or payload allows",
+ "type": "string"
+ },
+ "verdict": {
+ "description": "SAFE, CAUTION or RISK",
+ "type": "string"
+ }
+ },
+ "required": [
+ "verdict",
+ "explanation"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry behavioral information. It discloses that the tool works on provided data without requiring an on-chain lookup, which implies local processing. However, it does not state that the operation is read-only, side-effect-free, or what permissions it needs, leaving gaps that annotations would normally cover.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single efficient sentence that front-loads the core purpose and follows with the usage condition. No words are wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given a single-parameter tool with a complete schema and an output schema present, the description is nearly complete for invocation. Missing only explicit behavioral details (e.g., read-only nature) that annotations would have supplied, but these are not critical for an explain tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the parameter is fully documented in the schema. The description adds no additional semantics about the 'data' parameter beyond restating that it accepts an arbitrary approval/permission JSON payload, matching the schema's own description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb (Explain) and resource (approval/permission JSON payload), specifies scope (arbitrary) and output form (plain language). It distinguishes itself from sibling check_wallet_approvals by contrasting with 'an on-chain lookup', allowing an agent to identify the tool without opening schemas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives a clear condition for use ('when you already have the data') and an implicit alternative ('instead of needing an on-chain lookup'). It does not explicitly name the sibling tool check_wallet_approvals, but the contrast is sufficient for an agent to choose correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.