Skip to main content
Glama

Reissue the connection link

reissue_claim

Only with the agent token start_planner or start_subscription returned, and only until the person first opens a connection link: when they lost it (or it expired), returns a new single-use claimUrl for this token's own owner, valid for 24 hours, and the earlier unused link stops working. Give claimUrl only to that person; opening it saves their planner key in their browser. At most 3 a day. Once any link has been opened it answers 409 already_claimed: the person already has their key, in their saved planner link or through Restore on the planner page. Creates no account and charges nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reissue_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
claimUrlYes
expiresAtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations it discloses a great deal: 24-hour validity, single-use semantics, invalidation of the earlier unused link, a 3-per-day rate limit, the 409 error code, the side effect of saving the planner key in the browser, and that no account is created and nothing is charged. The one tension is that invalidating the previous link is a state-destroying side effect while destructiveHint=false, though 'destructive' is defensible here since no stored user data is removed; the description, not the annotation, is what makes that nuance visible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The gating condition is front-loaded ahead of behavior, and nearly every clause carries operational weight (validity window, daily cap, 409 path, non-billing). It is a single dense paragraph that would read faster broken into short clauses, but there is little genuine filler.

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 zero-parameter mutation tool with an output schema, everything an agent needs is present: preconditions, the 409 branch, rate limit, link lifetime, and the security warning to give claimUrl only to its owner. Return-shape detail is correctly left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning for the description to add. It correctly spends its words on preconditions and scope instead of inventing parameter prose.

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 names a specific verb+resource ('returns a new single-use claimUrl') and pins the exact precondition: the token must come from start_planner or start_subscription and the link must never have been opened. This cleanly separates it from the sibling token-creation tools and from Restore, so an agent can pick it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states when to call (the person lost or expired their link), when not to (once any link has been opened it answers 409 already_claimed), and what to do instead (their saved planner link or Restore on the planner page). Both the positive case and the exclusion are explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources