Skip to main content
Glama
Sign In

FabTally Safe

by io.github.zvmzaretsky
OverviewDiscussionsAdmin

Signature decode — type + summary + risk level (FREE)

decode_signature_free

FREE. Type + plain-English summary + risk level for an EIP-712 typed_data. Real result, no wallet. Upgrade to decode_signature for the full field-by-field decode + all risk flags + malicious-spender screening.

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": {
      "typed_data": "<typed_data>"
    },
    "name": "decode_signature_free"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoOptional chain override (else read from domain.chainId).
typed_dataYesEIP-712 typed data object: {domain, types, primaryType, message}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Since no annotations are provided, the description must carry the full burden. It states 'Real result, no wallet' which implies a live decode without side effects, and mentions it's a free version with limited scope. However, it does not disclose output format, error behavior, or any API key/auth requirements, so it only partially covers behavioral transparency.

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?

Four short sentences, each earning its place: 'FREE' states the cost, the core function is front-loaded, 'Real result, no wallet' adds behavioral context, and the upgrade path is clearly indicated. No fluff or repetition.

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 tool with a simple input schema (one required object, one optional string) and no output schema, the description explains the key return elements (type, summary, risk level) and the distinction from the full version. It is sufficient for an agent to understand the tool's purpose and invocation, though it stops short of describing the output structure in detail.

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% (both 'chain' and 'typed_data' have descriptions in the schema). The description itself adds no parameter-level detail beyond what the schema already states, so it meets the baseline for high schema coverage without providing extra value.

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 clearly states the tool's function: 'Type + plain-English summary + risk level for an EIP-712 typed_data.' It uses a specific resource (EIP-712 typed data) and distinguishes itself from the sibling tool decode_signature by being the free, summary-only version. The title also reinforces this.

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

Usage Guidelines5/5

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

Explicit usage guidance is provided: it's FREE, produces a real result without a wallet, and the description directly recommends 'Upgrade to decode_signature' when full field-by-field decoding is needed. This tells the agent when to use this tool versus the alternative.

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

All FabTally Safe toolsInspect
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.

Resources