Skip to main content
Glama
Sign In

InsureLink

by io.github.skewing1
OverviewDiscussionsAdmin

unsubscribe_attestation_freshness

Cancels a previously created attestation-freshness webhook subscription (also cancels the bundled reputation.drift channel on the same subscription). Free. Provide the subscription id returned by subscribe_attestation_freshness / POST /reputation-drift-subscribe. Remaining paid window is forfeited; no refund. Returns { ok, id, cancelled_at } on success.

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": {
      "id": "<id>"
    },
    "name": "unsubscribe_attestation_freshness"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSubscription id returned from subscribe_attestation_freshness or the paid /reputation-drift-subscribe response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that cancellation also removes the bundled reputation.drift channel, that the paid window is forfeited with no refund, and that the call is free, with the success return shape. This covers key side effects and financial impact, though it omits failure behavior and idempotency details.

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?

Three sentences, front-loaded with the core action, then the subscription-id source, and finally the financial caveat and return shape. No filler words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter unsubscribe tool with no output schema, the description provides all essential context: what is canceled, how to get the id, the cost implication, and the success response. It is adequately complete for an agent to select and invoke correctly.

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 input schema fully documents the single id parameter with 100% coverage. The description reinforces that the id comes from subscribe_attestation_freshness or POST /reputation-drift-subscribe, which duplicates the schema description and adds little new meaning.

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?

Description uses specific verb 'Cancels' and names the exact resource ('attestation-freshness webhook subscription'), plus the bundled reputation.drift channel. This clearly differentiates it from siblings like subscribe_attestation_freshness and list_attestation_freshness_subscriptions.

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?

States the tool is for canceling a previously created subscription and instructs where to find the subscription id (from subscribe_attestation_freshness or POST /reputation-drift-subscribe). It does not explicitly list when-not-to-use or alternative tools, but the context and sibling names make the intended use clear.

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