InsureLink

verify_attestation

Verifies an InsureLink reputation attestation for a wallet. Re-derives the signed payload server-side, recovers the EIP-191 signer, and returns { valid, signer, recovered, expires_at, checks }. Free.

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": {
      "wallet": "<wallet>"
    },
    "name": "verify_attestation"
  }
}

Input Schema

Name	Required	Description	Default
`wallet`	Yes	Wallet address (0x...)

Schema Changelog

Changes observed during successful MCP inspections.

AddedMay 8, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and delivers: it discloses server-side re-derivation of the payload, EIP-191 signer recovery, and the exact return object { valid, signer, recovered, expires_at, checks }. It also adds 'Free' to indicate cost. This is substantive behavioral context.

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 two sentences long, front-loaded with purpose, and contains no redundant information. Every sentence adds value.

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 simple tool with one parameter and no output schema, the description covers the process, the return shape, and cost. It doesn't explain the 'checks' field in detail, but overall it provides enough context for an AI agent to use the tool effectively.

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 coverage is 100% with one well-described parameter (wallet). The description adds no extra parameter semantics beyond the schema, but given the high coverage, the baseline of 3 is appropriate.

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: 'Verifies an InsureLink reputation attestation for a wallet.' It uses a specific verb (verifies) and resource (attestation), and distinguishes from siblings like get_attestation and verify_reputation_snapshot by focusing on attestation verification.

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?

Usage is implied: verify an attestation when needed. However, there is no explicit guidance on when to use this tool versus alternatives like verify_reputation_snapshot or get_attestation, and no exclusions are mentioned.

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

All InsureLink 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.

Resources

Need Help?