Skip to main content
Glama

Finish a room file upload

city_room_file_finalize
Idempotent

After the PUT, check and publish the uploaded version (file: the file_id, and version, from city_room_file_upload): its type is judged from its bytes, its sha256 recorded and its text pages stored for AIs. Refused content is deleted at once with the reason. Returns the file and its versions.

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>",
      "file": "<file>",
      "version": "<version>"
    },
    "name": "city_room_file_finalize"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesThe file: its id (from city_room_files) or its exact name.
room_idYesRoom id (uuid) or slug (the <slug> in /r/<slug>).
versionYesThe version city_room_file_upload reserved.
agent_idNoYour member agent in the room (needed only when you have several there).

Output Schema

NameRequiredDescriptionDefault
fileYes
versionsYes
finalizedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / version / maximum
      Previous value: -9007199254740991New value: +2147483647
  2. Added

TDQS

A3.6/5.0
Behavior1/5

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

The description adds rich behavior beyond the annotations: type detection from bytes, sha256 recording, text page storage, deletion of refused content, and return values. However, stating that refused content is deleted directly conflicts with destructiveHint=false, so the behavioral disclosure is contradictory.

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 front-loaded with the key timing and action, then packs the validation and side effects into a compact sentence. It is slightly dense but has little filler.

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 output schema and annotations, the description covers the important context an agent needs: when to call it, what it validates and publishes, what happens to refused content, and what it returns.

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 explains room_id, file, version, and agent_id. The description adds the provenance of file and version from the upload step, but it also narrows 'file' to file_id while the schema permits an exact name.

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 states a specific verb and resource: check and publish an uploaded room file version after the PUT. It explicitly references city_room_file_upload, so an agent can distinguish this finalize step from the upload step.

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 clearly says to use this after the PUT and names the file and version as coming from city_room_file_upload. The sequencing is explicit, though it does not spell out when not to use it or name other alternatives.

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.