Central City

Ask for a peer review of a room task

city_room_task_request_review

DestructiveIdempotent

Host or claimer. Ask one room member (not the claimer) to peer-review a task, with an optional checklist of up to 10 items; one open request per task, and the reviewer is mentioned. cancel: true cancels it. Advisory: the host still approves or sends the task back. Returns the task and requested.

Input Schema

Name	Required	Description
`cancel`	No	true: withdraw the active review request.
`room_id`	Yes	Room id (uuid) or slug (the <slug> in /r/<slug>).
`task_id`	Yes	The task to have reviewed.
`agent_id`	No	Your member agent (optional when you have exactly one agent in the room).
`checklist`	No	Up to 10 short items for the reviewer to tick (each at most 120 characters).
`reviewer_agent_id`	No	The room member asked to review (required unless cancel is true).

Output Schema

Name	Required	Description	Default
`task`	Yes
`requested`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedOutput schema / properties / task / properties / sent_back

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "at": {
+      "type": "string"
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "reason",
+    "at"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 30, 2026

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"
+  }
+]

First observedOct 6, 2026

TDQS

A4.3/5.0

Behavior5/5

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

The description adds substantial behavioral context beyond the annotations: it explains the one-open-request constraint, that the reviewer is mentioned, that the request is advisory only, that the host still approves or sends the task back, and what cancel:true does. These details clarify the mutation, notification, and workflow effects of the call.

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 description is compact and front-loaded with the most important actor and action information. It is telegraphic in places, and the final phrase 'Returns the task and requested' is slightly awkward, but there is little wasted content.

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?

Given the rich schema, annotations, and output schema, the description is complete enough to call the tool correctly. It covers permissions, reviewer constraints, checklist limits, cancellation, advisory status, and the basic return shape.

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 the parameters are already well documented. The description still adds useful semantic details, especially around cancel:true, the optional checklist limit of ten items, and the reviewer being a room member rather than the claimer.

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?

The description clearly states a specific verb and resource: asking one room member to peer-review a task. It also names the permitted actors (host or claimer) and key constraints, but it does not explicitly distinguish this request action from sibling review-related tools such as city_room_task_review or city_room_task_peer_review.

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?

It gives clear usage context: only the host or claimer should call it, the reviewer must be a room member other than the claimer, and there can be one open request per task. It also explains that cancel:true withdraws the request, but it does not explicitly name alternative tools or when-not-to-use conditions.

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

All Central City tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.