Skip to main content
Glama

vibedeploy

by be.vibedeploy

Add files to a staging session

add_files
Idempotent

Append files to an open staging session. Call as many times as needed; commit_deploy applies them all at once. Validates path/extension/encoding on every call so a bad file fails fast. Same 500 MB cap as single-call deploys, but cumulative across the session. LARGE TEXT FILES: a file that looks too big to inline (100-250 KB of HTML/CSS/JS) usually still fits in ONE call — gzip it locally, base64 the result, send with encoding:'gzip+base64' (text compresses 3-5×, so ~250 KB of source ≈ ~70 KB on the wire). Prefer that over add_file_chunk: one call, no ordering hazards. Only chunk when a single file exceeds ~250 KB of source even after gzip, or when you have no way to gzip locally. If your environment can run shell but can't reach this host, gzip+base64 via add_files is the fastest path; if it CAN reach this host, begin_deploy's uploadUrl (tarball POST, 100 MB) beats everything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesYesFiles to append to the staging scratch dir. Same wire shape as deploy_site/update_site — array form supports binary via encoding:'base64'; map form is utf8-only. Re-adding a path overwrites the previously staged version. Cumulative cap across the whole session: 500 MB.
deployIdYesSession id returned by begin_deploy.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
deployIdYes
warningsNo
filesAddedYesFiles written by this call.
request_idNoServer-assigned request correlation id. Quote it when contacting support.
totalBytesYesTotal bytes staged so far across all add_files calls.
totalFilesYesTotal files now in the scratch dir.
remainingBudgetYesBytes still available before hitting the 500 MB cap.

TDQS

A4.9/5.0
Behavior5/5

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

Beyond annotations (idempotent, not destructive), the description reveals: cumulative 500 MB cap, per-call validation with fast fail, file overwrite on re-add, and detailed encoding behavior with compression ratios. It discloses all important behavioral traits without contradicting annotations.

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 front-loaded with the core purpose and includes multiple paragraphs. While dense, every sentence adds value (usage guidance, encoding advice, comparisons). It is not overly terse but efficiently packs necessary information, slightly exceeding minimum conciseness.

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?

Given the tool's complexity (encoding options, sibling comparisons, cumulative cap) and the presence of an output schema (so return values need not be explained), the description covers all essential aspects: purpose, usage guidance, limitations, encoding details, and alternatives. No gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the description adds substantial value: it explains encoding compression ratios (gzip+base64), cumulative file-size cap, path overwrite semantics, and the wire-shape alternatives. It enriches the schema with practical, actionable context.

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 clearly states the verb 'Append files' and the resource 'open staging session'. It differentiates from sibling tools like add_file_chunk by explaining when to prefer add_files over chunking, and also mentions begin_deploy's uploadUrl for large payloads. The verb-resource pair is specific and distinct.

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?

The description provides explicit when-to-use and when-not-to-use guidance. It advises preferring add_files over add_file_chunk for files compressible to ~250 KB or less, and only chunking when necessary. It also notes begin_deploy's uploadUrl as a faster alternative for large tarballs. This helps the agent choose correctly.

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

All vibedeploy toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose, from deployment and file management to domain configuration and analytics. Even similar-sounding tools like add_files and add_file_chunk are well-differentiated by context and use case.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (e.g., add_custom_domain, list_sites, delete_source_file). The naming is predictable and easy to understand.

Tool Count4/5

39 tools is higher than the typical 3-15 range, but each tool serves a necessary function for a comprehensive deployment platform. The count is justified by the broad feature set, though slightly heavy.

Completeness5/5

The tool set covers the full lifecycle of site deployment, management, backup, custom domains, form handling, analytics, and source editing. There are no obvious gaps for the intended functionality.

Resources