On Board

Overview Schema Source Related Servers Discussions Admin

memory_claim_ticket

Idempotent

Claim an open ticket to take ownership, and call again to move it to in_progress when work begins. This helps agents manage task status in shared project memory.

Instructions

Claim an open ticket (sets to claimed). Call again on a claimed ticket to advance to in_progress (e.g. when spawning a subagent).

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": {
      "params": "<params>"
    },
    "name": "memory_claim_ticket"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.0.4Aug 3, 2026

TDQS

B3.1/5.0

Behavior1/5

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

The description directly contradicts the idempotentHint annotation. It states that calling again on a claimed ticket advances to in_progress, meaning repeated calls have different effects, violating idempotency. No other behavioral details (e.g., error conditions, permissions) are provided.

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 concise (two sentences) and front-loaded with the action. It conveys the primary behavior and an important nuance (second call advances state) without unnecessary words or repetition.

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?

Despite having an output schema, the description is incomplete. The contradiction with idempotency is a critical gap, and the description does not clarify edge cases (e.g., what happens if the ticket is already in_progress). Missing parameter guidance also reduces completeness.

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

Parameters1/5

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

The description provides no explanation for the parameters ticket_id and agent_name. The input schema only describes ticket_id as 'Ticket ID to claim', while agent_name has no description. With 0% schema description coverage from the tool description, the agent is left without guidance on what these parameters mean or how to format them.

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 clearly states the tool's purpose: claiming an open ticket, with a specific verb ('Claim') and resource ('ticket'). It also distinguishes itself from sibling ticket tools (create, cancel, submit, etc.) by detailing the state transition behavior. The added note about advancing to in_progress on a second call further clarifies the tool's unique role.

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?

The description provides clear context for when to use the tool: claim an open ticket, and recall it on a claimed ticket to advance to in_progress, e.g., when spawning a subagent. However, it does not explicitly mention alternatives or when not to use it, so it lacks exclusionary guidance.

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