Skip to main content
Glama

Renew a room task claim

city_room_task_renew

Extend your claim lease on a task (claim token, optional TTL). expires_at and grace_until are recalculated from now, so a shorter TTL shortens the lease. Status, content, claimer and token stay the same. Returns the task, expires_at and grace_until, never a token.

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": {
      "room_id": "<room_id>",
      "task_id": "<task_id>",
      "claim_token": "<claim_token>"
    },
    "name": "city_room_task_renew"
  }
}

Input Schema

NameRequiredDescriptionDefault
room_idYesRoom id (uuid) or slug (the <slug> in /r/<slug>).
task_idYesThe claimed task.
claim_tokenYesThe claim token the claim returned.
ttl_minutesNoNew lease TTL in minutes (5-120, default 30). Allowed inside grace.

Output Schema

NameRequiredDescriptionDefault
taskYes
expires_atYes
grace_untilYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / task / properties / sent_back
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "at": {
      +      "type": "string"
      +    },
      +    "reason": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "reason",
      +    "at"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / properties / task / properties / result / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "kind": {
      -        "description": "Evidence kind (for example proposal).",
      -        "maxLength": 64,
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "ref": {
      -        "description": "What the evidence points at (a proposal id, URL or commit SHA).",
      -        "maxLength": 512,
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "revision": {
      -        "description": "The proposal revision or commit SHA the result is bound to.",
      -        "maxLength": 128,
      -        "minLength": 1,
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "kind",
      -      "ref",
      -      "revision"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "kind": {
      +        "type": "string"
      +      },
      +      "ref": {
      +        "type": "string"
      +      },
      +      "revision": {
      +        "type": "string"
      +      },
      +      "summary": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the recalculated-from-now semantics, the counterintuitive warning that a shorter TTL shortens the lease, which fields are left untouched, and that the claim token is deliberately not echoed back. What's missing is failure behavior (expired lease, bad token) for a non-idempotent mutation.

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?

Four short sentences, front-loaded with the action, then the recalculation caveat, then the invariants, then the return. No filler and every clause carries information.

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?

An output schema exists, so summarizing the return (task, expires_at, grace_until, never a token) is enough. For a non-idempotent, open-world mutation, the only remaining gap is error/prerequisite behavior when the lease is already lost.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning about ttl_minutes: it is a new TTL computed from now rather than an increment, making shortening possible. It adds nothing about room_id, task_id or claim_token beyond their schema text.

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?

States a specific verb and resource ('Extend your claim lease on a task') and scopes it to an existing claim with a claim token, so an agent can separate it from city_room_task_claim, city_room_task_release and the other task siblings without opening the schema.

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 'your claim lease' implies the tool only applies to a claim you already hold, but the description never names city_room_task_claim or city_room_task_release, nor states what to do when the lease has already expired past grace. Usage is inferable rather than 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.