Skip to main content
Glama
Sign In

InsureLink

by io.github.skewing1
OverviewDiscussionsAdmin

verify_reputation_snapshot

Compares a wallet's latest stored reputation_history snapshot against a fresh live cross-chain reputation computation. Returns { snapshot, live, match, drift, signature, signer } so counterparty agents can confirm an advertised score isn't stale before transacting. Signed EIP-191 by the InsureLink platform key. Requires x402 payment ($0.001). Returns payment instructions.

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_reputation_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesWallet address whose snapshot to verify against live reputation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses key behavioral aspects: the tool requires a $0.001 x402 payment, returns a signed EIP-191 signature by the InsureLink platform key, and returns payment instructions. This goes beyond basic operation and warns of cost and security, though it doesn't mention error conditions or potential side effects beyond payment.

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 three sentences, each delivering essential information without redundancy. It front-loads the primary action, then details the return values and payment requirement. Every sentence earns its place.

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?

Given a single parameter, no output schema, and no annotations, the description covers the essential invocation details: the wallet input, the return fields (snapshot, live, match, drift, signature, signer), the cost, and the payment instructions. It lacks explicit failure-mode handling but is otherwise complete for an agent to invoke the tool.

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?

The schema already provides a clear description of the wallet parameter with type, pattern, and description. The tool description doesn't add additional meaning or syntax details beyond what the schema supplies, 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 clearly states the tool's function with a specific verb ('compares') and resource ('wallet's latest stored reputation_history snapshot against a fresh live cross-chain reputation computation'). It also distinguishes itself from siblings by focusing on verifying snapshot freshness with a signed response, which is unique among the listed tools.

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 provides clear context for when to use the tool: 'so counterparty agents can confirm an advertised score isn't stale before transacting'. It doesn't explicitly name alternatives or exclusions, but the use case is sufficiently scoped to guide an agent.

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

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