Skip to main content
Glama

Deploy text files

deploy_text_files
DestructiveIdempotent

Publishes up to 1 MiB of UTF-8 files to an exact existing static project using durable validation and revision checks. A root index.html is required. The returned deployment reports queued, failed or active publication.

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": {
      "project_id": "<project_id>",
      "files": "<files>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "deploy_text_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYes
project_idYesExact stable project ID. Resolve it first. Never invent an update target.
auto_activateNo
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.
expected_revisionNoOriginal base_revision in local .deploymonster.json; never substitute current server revision before reconciliation.
overwrite_revisionNoExact remote revision the USER explicitly agreed to overwrite after seeing change summary.
overwrite_confirmationNoOnly after explicit user overwrite choice; never auto-confirm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, openWorld=true, but the description adds genuinely new behavior: the 1 MiB/UTF-8 payload ceiling, the mandatory root index.html, durable validation and revision checks, and the possible returned states (queued, failed, active). It does not explain what an overwrite does to existing remote files, which is the main remaining destructive-behavior gap.

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?

Three tight sentences, front-loaded with the action and its size/format constraint before the prerequisites and return states. 'Durable validation and revision checks' is slightly jargon-heavy but still carries meaning about conflict handling.

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?

For a destructive 7-parameter write tool with no output schema, the description covers the payload limits, the required index.html, the validation/revision model, and the shape of the returned deployment status. What is missing is the failure/conflict path (what happens when expected_revision mismatches) and guidance versus the begin/finalize deployment siblings.

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 coverage is 71% and the revision/overwrite/idempotency parameters already carry strong inline descriptions, so the schema does most of the work. The description adds only the file-content constraint (UTF-8, 1 MiB, root index.html) and says nothing about project_id resolution, auto_activate, or the overwrite confirmation flow beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (publishes) and resource (UTF-8 text files) plus hard scope limits (1 MiB, exact existing static project), which separates it from generic deployment siblings like begin_deployment. It does not explicitly name any sibling as the alternative, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

'An exact existing static project' and 'A root index.html is required' imply preconditions but never frame them as when-to-use guidance, and no alternative tool is named for related cases (e.g. beginning or finalizing a deployment). Usage is only implied, leaving the agent to infer the routing decision.

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.

Resources