Skip to main content
Glama
Sign In

TestGraph

by io.github.BBCBasic
OverviewDiscussionsAdmin

Claim an open deliberation

claim_deliberation
Idempotent

Atomically claim an open deliberation for the authenticated MCP client. Repeating the same claim is safe; a different client receives DELIBERATION_ALREADY_CLAIMED. Claiming grants no authority outside the stored deliberation scope.

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": {
      "deliberation_id": "<deliberation_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "claim_deliberation"
  }
}

Input Schema

NameRequiredDescriptionDefault
source_modelNo
deliberation_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / version_check
      Removed value: -{
-  "description": "Required live deployment token. Call get_server_info immediately before this write and pass write_version_token unchanged. Stale or missing tokens are rejected before any write occurs.",
-  "maxLength": 64,
-  "minLength": 64,
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "deliberation_id",
-  "idempotency_key",
-  "version_check"
-]New value: +[
+  "deliberation_id",
+  "idempotency_key"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / version_check
      Added value: +{
+  "description": "Required live deployment token. Call get_server_info immediately before this write and pass write_version_token unchanged. Stale or missing tokens are rejected before any write occurs.",
+  "maxLength": 64,
+  "minLength": 64,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "deliberation_id",
-  "idempotency_key"
-]New value: +[
+  "deliberation_id",
+  "idempotency_key",
+  "version_check"
+]
  3. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the idempotentHint annotation, the description adds concrete behavioral detail: atomic claiming, safe repetition, the DELIBERATION_ALREADY_CLAIMED error condition, and the scope limitation that claiming grants no authority beyond the stored deliberation. This meaningfully enriches what annotations alone convey.

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?

Three sentences with no filler. The core action is front-loaded, and the second and third sentences add important behavioral caveats. Every sentence earns its place.

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

Completeness3/5

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

The description covers claim semantics and conflict behavior well, and annotations handle idempotency and safety. However, with no output schema and no parameter-level explanation, an agent still lacks clarity about expected return values and the optional source_model field.

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 0%, so the description must compensate. It does not explain deliberation_id, idempotency_key construction, or the optional source_model parameter. The 'repeating the same claim is safe' sentence hints at idempotency_key semantics, but the mapping is implicit rather than explicit.

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 uses a specific verb ('claim'), names the resource ('open deliberation'), and identifies the actor ('authenticated MCP client'). It also conveys atomicity, which distinguishes this from sibling create/get/list tools even without naming them.

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 clearly implies when to use the tool: when you want to claim an open deliberation. However, it gives no explicit guidance about alternatives, exclusions, or prerequisite steps such as listing open deliberations first.

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

All TestGraph 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