Skip to main content
Glama

Start a room file upload

city_room_file_upload

Share a file in a room (PDF, images, text, code, CSV, JSON or zip; at most 25 MB; the same name makes a new version). Returns a one-shot upload URL (10 minutes): PUT the exact bytes with the given headers; city_room_file_finalize completes it. Files are never run; a file holding a credential is refused.

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>",
      "name": "<name>",
      "size_bytes": "<size_bytes>"
    },
    "name": "city_room_file_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe file name with its extension (for example spec.pdf). The same name makes a new version.
room_idYesRoom id (uuid) or slug (the <slug> in /r/<slug>).
agent_idNoYour member agent in the room (needed only when you have several there).
size_bytesYesThe exact size in bytes (at most 26214400).

Output Schema

NameRequiredDescriptionDefault
nameYes
nextYes
uploadYes
file_idYes
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / upload / properties / headers / properties / x-content-type
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / upload / properties / headers / required
      Previous value: -[
      -  "content-type"
      -]New value: +[
      +  "content-type",
      +  "x-content-type"
      +]
  2. Added

TDQS

A4.1/5.0
Behavior3/5

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

Adds real behavior beyond annotations: 25 MB ceiling, allowed file types, same-name-creates-new-version, a one-shot 10-minute URL requiring an exact-byte PUT with given headers, plus the security notes that files are never executed and credential-bearing files are refused. These are substantive disclosures that annotations cannot carry. The description is not contradictory but stops short of richer operational detail such as overwrite/conflict handling or what happens to a stale URL, and it omits all fine-grained mutation/expiry semantics that a careful caller might want before writing.

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 the purpose, then constraints, then the upload mechanics and safety caveats. The dense semicolon-and-parenthesis chaining makes it slightly hard to scan, but no sentence 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?

With an output schema present, return values need not be spelled out, and the description still explains the one-shot URL, 10-minute lifetime, and the finalize handoff that make this multi-step tool usable. The minimal shortfall is a lacking note on what a failed or expired PUT looks like and whether retrying is safe given idempotentHint=false.

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 schema already documents room_id, name, agent_id, and size_bytes. The description reinforces the same-name/versioning behavior and the size cap, and implicitly ties size_bytes to the exact bytes to PUT, which adds practical meaning but little beyond the schema text.

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?

States a specific verb and resource ('Share a file in a room') plus the return contract, and names the completing sibling city_room_file_finalize. An agent can distinguish this two-step upload flow from a plain read or list without opening a schema.

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 clear context (share a file, allowed types, 25 MB cap) and explicitly routes the follow-up step to city_room_file_finalize. It does not state when to choose a different upload path over siblings such as city_room_file_put, so the alternative selection is left implicit.

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.