TeamShared

file_upload_request

Get a one-time uploader script to push a local file into a shared file.

For large local HTML/Markdown files that don't fit inline in file_create/file_update. Returns upload_url, upload_token, an expires_in_seconds TTL, and a self-deleting Python script. Save the script to disk and run python3 upload.py /path/to/file; it reads the file, POSTs it to the server with the one-time token, prints the resulting file id (and public URL if publish=true), and deletes itself on success. The token is single-use and expires in ~10 min.

Update mode: pass file_id to append the uploaded body as a new version to an existing shared file (the title is ignored; the existing file's title/slug/share_token are preserved, and the bucket mirror is re-published to the new version when the file is already published). This is the supported way to push a new version of a large file.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`agent`	No	Override agent identity
`title`	Yes	File title (used only when creating a new file; ignored in update mode)
`file_id`	No	Existing file UUID to append a new version to (update mode). Omit to create a new file.
`publish`	No	If true, the file is published immediately (returns public URLs). In update mode this is idempotent if already published.
`work_id`	No	Attach the uploaded file to this work item UUID
`filename`	No	Optional filename (used for format sniffing and as the script's default path)
`project_id`	No	Attach the uploaded file to this project UUID (kind=artifact)
`content_format`	No	'html', 'markdown', 'diagram' (teamshared.diagram/v1 JSON/YAML), 'sheet' (teamshared.sheet/v1 JSON/YAML), or 'auto' (sniff from the file extension; .diagram.yaml/json, .sheet.json/yaml)	auto
`upload_base_url`	No	Optional server origin (e.g. https://teamshared.com). Defaults to settings.public_url.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 8, 2026

changedInput schema / properties / content_format / description

Previous value: -"'html', 'markdown', 'diagram' (teamshared.diagram/v1 JSON/YAML), or 'auto' (sniff from the file extension; *.diagram.yaml/json)"New value: +"'html', 'markdown', 'diagram' (teamshared.diagram/v1 JSON/YAML), 'sheet' (teamshared.sheet/v1 JSON/YAML), or 'auto' (sniff from the file extension; *.diagram.yaml/json, *.sheet.json/yaml)"

Changed2 schema fields changedSep 5, 2026

changedInput schema / properties / content_format / description

Previous value: -"'html', 'markdown', or 'auto' (sniff from the file extension)"New value: +"'html', 'markdown', 'diagram' (teamshared.diagram/v1 JSON/YAML), or 'auto' (sniff from the file extension; *.diagram.yaml/json)"

addedInput schema / properties / project_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Attach the uploaded file to this project UUID (kind=artifact)"
+}

Changed1 schema field changedAug 31, 2026

addedInput schema / properties / work_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Attach the uploaded file to this work item UUID"
+}

First observedAug 18, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations, the description carries full burdencents for behavioral disclosure. It thoroughly describes the script's lifecycle (reads file, POSTs, prints id/URL, deletes itself on success), token security (single-use, ~10 min expiry), and update-mode side effects (preserves title/slug/share_token, re-publishes mirror). This goes well beyond a simple API call description.

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 somewhat long but well-structured with a main paragraph, a code-execution block, and a dedicated 'Update mode' section. Information is front-loaded with the core purpose, and every sentence contributes to usage or behavior. Slight verbosity in the script walkthrough prevents a perfect score.

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?

For a complex tool with 9 parameters and an output schema, the description covers all essential aspects: when to use, full script execution flow, return values, update-mode semantics, and token lifecycle. Output schema already documents return fields, so the description needn't repeat them. No significant missing information for correct invocation.

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 baseline is 3. The description adds contextual nuance like 'title ignored in update mode' and the script's behavior related to publish, but these are also present in the schema's field descriptions. The description doesn't add significant new parameter semantics beyond what the schema already documents.

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 ('Get... push'), a resource ('a local file into a shared file'), and explicitly distinguishes itself from file_create/file_update by specifying its use case for large files that don't fit inline. This clearly separates it from siblings.

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?

Explicitly states when to use this tool ('For large local HTML/Markdown files that don't fit inline in file_create/file_update') and provides a specific alternative path for updating ('pass file_id'). It also labels update mode as 'the supported way to push a new version of a large file,' giving clear routing guidance.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.