Skip to main content
Glama

renew

Extend an active, unexpired lease from the current time so AI agents can maintain coordinated ownership of a shared topic.

Instructions

Extend your existing, unexpired lease from the current time.

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": {
      "topic": "<topic>",
      "token": "<token>"
    },
    "name": "renew"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlNo
tokenYesThe private token returned by lock for this lease.
topicYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the description carries most of the burden. It discloses two real behavioral facts — the lease must already exist and be unexpired, and the new window is measured "from the current time" — but says nothing about failure behavior for an expired/unknown lease, whether the token stays valid, or how this affects remaining time.

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?

A single front-loaded sentence with zero filler; the precondition and the time anchor are both packed into it economically.

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?

For a state-mutating tool with no output schema, 33% schema coverage and minimal annotations, the definition leaves too much open: no return information (new expiry? same token?), no failure semantics, and no explanation of two of its three parameters. It is too sparse for the tool's complexity.

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

Parameters2/5

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

Schema description coverage is only 33%: token is documented in the schema but ttl and topic are bare. The description's "from the current time" gives a hint about ttl's anchor point, but it never explains ttl units/limits, the 1800 default behavior, or what topic identifies — leaving two of three parameters semantically thin.

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?

"Extend your existing, unexpired lease" gives a specific verb (extend) and resource (lease), with a precondition that implicitly separates it from the acquiring sibling (lock). An agent can tell this is not a lease-creation or release operation, though the description never names the alternative tools explicitly.

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 phrase "existing, unexpired lease" implies this is only for leases you already hold, which is useful routing context, but there is no explicit statement of when to prefer this over lock/unlock or what to do if the lease has lapsed. Usage must be inferred.

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

Deploy Server

Other Tools