Skip to main content
Glama
Sign In

InsureLink

by io.github.skewing1
OverviewDiscussionsAdmin

renew_sla

Renews an existing SLA agreement. Requires x402 payment ($0.005). 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": {
      "tokenId": "<tokenId>"
    },
    "name": "renew_sla"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenIdYesSLA token ID
durationNoRenewal duration (5, 7, or 10 years)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It discloses the payment requirement and that it 'Returns payment instructions', but does not clarify whether the tool actually renews the SLA immediately or only initiates a payment flow. This ambiguity is a significant transparency gap for a paid mutation tool.

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 short sentences, front-loaded with the core action, and contains no filler. Every word earns its place.

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

Completeness2/5

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

The tool is a paid renewal action with no annotations or output schema, yet the description fails to explain the full flow (whether payment is executed, whether renewal is immediate, what happens after payment). This ambiguity is critical for an agent to invoke correctly, making the description incomplete.

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%, so the baseline is 3. The description adds no extra parameter meaning beyond what the schema already provides (e.g., duration options are already listed in the schema).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool 'Renews an existing SLA agreement' with a specific verb and resource. It implies distinction from minting by using 'existing', but does not explicitly name sibling alternatives like mint_sla, so it falls short of full differentiation.

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?

The description implies usage for existing SLAs and mentions the x402 payment requirement. However, it provides no explicit when-to-use vs alternatives, no exclusions, and no context about when not to use it.

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