Skip to main content
Glama

TeamShared

by io.github.xhad
OverviewDiscussionsAdmin

file_update

Append a new version to an existing shared file.

Omit expected_version to append prior-max-plus-one. Pass the version from file_get when editing a shared file so a concurrent writer is not overwritten. A mismatch writes nothing and returns status=conflict. If the file is published, a successful new version is eagerly mirrored to the Railway bucket. Old versions are never mutated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentNoOverride agent identity
contentYesNew file body (markdown, raw HTML, teamshared.diagram/v1 or teamshared.diagram/v2, or teamshared.sheet/v1 JSON/YAML)
file_idYesFile UUID to update
content_formatNoOverride content format ('markdown', 'html', 'diagram', or 'sheet'); defaults to the file's current format
expected_versionNoLatest version from file_get. Omit to append unconditionally. A mismatch writes nothing and returns status=conflict with current_version, current_body (file content), updated_by, and updated_at.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / expected_version
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Latest version from file_get. Omit to append unconditionally. A mismatch writes nothing and returns status=conflict with current_version, current_body (file content), updated_by, and updated_at."
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / content / description
      Previous value: -"New file body (markdown, raw HTML, teamshared.diagram/v1, or teamshared.sheet/v1 JSON/YAML)"New value: +"New file body (markdown, raw HTML, teamshared.diagram/v1 or teamshared.diagram/v2, or teamshared.sheet/v1 JSON/YAML)"
  3. Changed2 schema fields changed
    • changedInput schema / properties / content / description
      Previous value: -"New file body (markdown, raw HTML, or teamshared.diagram/v1 JSON/YAML)"New value: +"New file body (markdown, raw HTML, teamshared.diagram/v1, or teamshared.sheet/v1 JSON/YAML)"
    • changedInput schema / properties / content_format / description
      Previous value: -"Override content format ('markdown', 'html', or 'diagram'); defaults to the file's current format"New value: +"Override content format ('markdown', 'html', 'diagram', or 'sheet'); defaults to the file's current format"
  4. Changed2 schema fields changed
    • changedInput schema / properties / content / description
      Previous value: -"New file body (markdown or raw HTML)"New value: +"New file body (markdown, raw HTML, or teamshared.diagram/v1 JSON/YAML)"
    • changedInput schema / properties / content_format / description
      Previous value: -"Override content format ('markdown' or 'html'); defaults to the file's current format"New value: +"Override content format ('markdown', 'html', or 'diagram'); defaults to the file's current format"
  5. First observed

TDQS

A4.7/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 richly: concurrency semantics (mismatch writes nothing, returns status=conflict), versioning invariant (old versions never mutated, append at prior-max-plus-one), and the side effect of eager mirroring to the Railway bucket for published files. This is exactly the behavioral context an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then the conditional and side-effect details. Every sentence adds information; nothing is padding.

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 mutation tool with no annotations, it covers conflict behavior, versioning invariants, and publish side effects. An output schema exists, so return-value details are not needed in the description.

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 the intent behind expected_version (guarding against a concurrent writer) and points to file_get as the source of the version value, which goes beyond the schema's mechanical conflict description.

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 ('Append a new version to an existing shared file'), which cleanly separates it from file_create (new file) and file_get (read). An agent can identify the operation and target without opening the 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 explicit conditional guidance for the key parameter: pass version from file_get when editing a shared file to avoid clobbering a concurrent writer, omit expected_version to append unconditionally. It does not explicitly contrast with file_create for new files, so the routing is implied rather than named.

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

All TeamShared toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources