Skip to main content
Glama
Sign In

InsureLink

by io.github.skewing1
OverviewDiscussionsAdmin

subscribe_reputation_drift_alerts

Subscribes a webhook URL to receive signed POST notifications whenever a watched wallet's reputation snapshot drifts beyond the configured threshold (score delta and/or tier change). 30-day paid window per subscription. The reputation-drift-monitor cron evaluates active subscriptions and POSTs { event:'reputation.drift', wallet, previous, current, drift, observed_at, subscription_id } to callback_url. Use to be notified the moment a counterparty's reputation degrades — replaces polling /cross-chain-reputation. Requires x402 payment ($0.01). 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>",
      "callback_url": "<callback_url>"
    },
    "name": "subscribe_reputation_drift_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesWallet address to monitor for reputation drift.
callback_urlYesHTTPS endpoint that will receive POST drift alerts.
duration_daysNoLength of the paid monitoring window in days. Default 30.
threshold_scoreNoMinimum |score_delta| that triggers a POST. Default 5.
max_notificationsNoCap on POST alerts before subscription auto-exhausts. Default 100.
threshold_tier_changeNoIf true (default), any tier flip (Bronze↔Silver↔Gold↔Platinum) fires regardless of score_delta.

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, the description carries the full burden of behavioral disclosure. It reveals that notifications are signed POSTs, that a cron evaluates active subscriptions, the exact payload format, a 30-day paid window, and that payment is required ($0.01) with payment instructions returned. This is substantial transparency, though it doesn't cover failure modes or what happens after payment is made.

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 well-structured and front-loaded with the core purpose, followed by key details (payload, use case, payment). Every sentence adds value, and the length is appropriate for a tool with no annotations and no output schema. It avoids redundancy and is easy to scan.

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 the tool has 6 parameters and no output schema, the description provides a strong contextual picture: what it does, when to use it, how it works (cron, payload), cost, and what to expect in return (payment instructions). It doesn't detail the full payment flow or what happens after payment, but it covers the essential operational aspects for an agent to select and 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?

Schema description coverage is 100%, so the baseline is 3. The description reinforces some schema terms (e.g., 'score delta' relating to threshold_score, 'tier change' relating to threshold_tier_change) and mentions the default 30-day window, but it doesn't add significant meaning beyond the schema's parameter descriptions. It doesn't mention max_notifications or duration_days explicitly, but those are already well-described in the schema.

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: subscribing a webhook URL to receive signed POST notifications on reputation drift. It names the specific resource (reputation snapshot drift) and differentiates from sibling tools like subscribe_attestation_freshness by focusing on reputation drift rather than attestation freshness. The explicit phrase 'replaces polling /cross-chain-reputation' further clarifies its distinct purpose.

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 a clear use case: 'Use to be notified the moment a counterparty's reputation degrades' and names an alternative (polling /cross-chain-reputation). It does not explicitly state when not to use the tool, but the context is sufficient for an agent to understand when it is appropriate. The mention of a paid window ($0.01) also signals a cost consideration that should inform usage.

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