TeamShared

storage_upload_request

Mint a one-time uploader script for a private Storage blob (any file type).

Storage is the org's binary store: bytes go to the Railway bucket, metadata to storage_objects. Objects stay private until a human seat calls storage_publish (agent seats must request_gated_approval(gate=publish)). Document MIME types (Markdown, HTML, plain text, diagram JSON/YAML) are stored as blobs; versioned edit / /s/ publish still use file_upload_request. Pass work_id and/or project_id to attach after ingest (kind=artifact; transcripts stay on shared files). Pass parent_id to place the file in a folder. Batch uploads are multiple grants (one file each) — console multi-select uses sequential ingest, not a multi-file grant. Returns upload_url, upload_token, max_bytes, and a self-deleting Python script. Token is single-use and expires in ~10 min.

Input Schema

Name	Required	Description
`agent`	No	Override agent identity
`title`	Yes	Storage object title
`work_id`	No	Attach the uploaded Storage object to this work item UUID
`filename`	No	Optional local filename (script default path + MIME sniff)
`parent_id`	No	Folder UUID to land the file in (omit or empty = org root). One grant per file.
`project_id`	No	Attach the uploaded Storage object to this project UUID (kind=artifact)
`content_type`	No	Optional MIME type hint stored on the grant
`upload_base_url`	No	Optional server origin (e.g. https://teamshared.com). Defaults to settings.public_url.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 5, 2026

addedInput schema / properties / parent_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Folder UUID to land the file in (omit or empty = org root). One grant per file."
+}

AddedSep 5, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so: objects remain private until publish, publishing is gated for agent seats, the token is single-use and expires in ~10 minutes, and the returned script is self-deleting. It also discloses the batch semantics (one grant per file) that would otherwise cause failed calls.

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 and dense with no filler sentences for an operation this complex. A few constructions are compressed to the point of being cryptic, notably 'versioned edit / /s/ publish still use file_upload_request', which costs some readability.

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?

An output schema exists, yet the description still names the key return fields (upload_url, upload_token, max_bytes, script) and their lifetimes. Privacy model, gating path, attachment semantics, and folder placement are all covered for an 8-parameter mutation-adjacent tool.

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 baseline is 3; the description adds real meaning on top by explaining that work_id/project_id attach after ingest as kind=artifact, that transcripts must stay on shared files, and that parent_id controls folder placement with one grant per file. It does not add much on agent, filename, content_type, or upload_base_url 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?

Opens with a specific verb and resource: 'Mint a one-time uploader script for a private Storage blob (any file type).' It also contrasts itself with the closest sibling, stating that versioned edit and /s/ publish still use file_upload_request, so an agent can distinguish the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing is given: agents must call request_gated_approval(gate=publish) while human seats call storage_publish; documents/transcripts stay on file_upload_request; batch uploads are multiple single-file grants, not one multi-file grant. It names the alternatives and the conditions that select them.

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

All TeamShared tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.