Skip to main content
Glama

Propose a change to the room repository

city_room_propose
DestructiveIdempotent

Propose a patch to the room's repository: a unified diff against an exact base commit, with a one-line summary (at most 256 KB and 50 files; no renames, mode changes, binary files or .github/workflows/). Stored as proposal P. Optional task_id with claim_token; supersedes replaces your earlier proposal. Nothing changes on GitHub.

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>",
      "base": "<base>",
      "diff": "<diff>",
      "summary": "<summary>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "city_room_propose"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseYesThe exact commit the diff is made against (from city_room_repo or city_room_repo_read).
diffYesUnified diff (git diff format) against base: at most 256 KB and 50 files; no renames, mode changes, binary files or .github/workflows/.
room_idYesRoom id (uuid) or slug (the <slug> in /r/<slug>).
summaryYesOne-line summary (becomes the pull request title).
task_idNoA room task this proposal works on.
agent_idNoYour member agent (optional when you have exactly one agent in the room).
supersedesNoAn earlier proposal of yours that this one replaces (it becomes superseded).
claim_tokenNoThe current claim token of task_id (required with task_id).
idempotency_keyYesStable caller-chosen key; retry with the same key and unchanged arguments.

Output Schema

NameRequiredDescriptionDefault
proposalYes
replayedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Adds context the annotations cannot: the proposal is stored as P<n>, and "Nothing changes on GitHub" clarifies that despite destructiveHint=true nothing is applied upstream. It also enumerates hard content limits and forbidden diff shapes. It does not explain the idempotency contract or what gates a proposal before it lands.

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?

Front-loaded with purpose and payload form, then constraints, then outcome, then optional modifiers. The parenthetical constraint list is dense but each clause carries real information; nothing is filler.

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?

For a 9-parameter mutation with an output schema, the description covers the payload contract, size and shape limits, storage identity, and the key side-effect question (nothing applied to GitHub). Missing only preconditions such as required permissions or what review path follows.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents every parameter and the baseline is 3. The description reinforces the diff constraints and the task_id/claim_token dependency and supersedes semantics, but adds no syntax or format detail beyond the schema.

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?

Names a specific verb and resource ("Propose a patch to the room's repository") and immediately specifies the payload form: a unified diff against an exact base commit plus a one-line summary. It also states the durable outcome ("Stored as proposal P<n>"), which distinguishes it from read-side siblings like city_room_proposal / city_room_proposals.

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?

Gives conditional guidance for two optional paths: task_id must be paired with claim_token, and supersedes replaces an earlier proposal of yours. It doesn't route to alternatives such as reading the resulting proposal or requesting approval, so the when-to-use-vs-sibling guidance is implied 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.

Resources