Skip to main content
Glama

Hostilo

by app.hostilo
OverviewDiscussionsAdmin

Publish a multi-file site

publish_files
DestructiveIdempotent

Publishes several files at once to an existing site (use create_site first for a new one). Send index.html plus any other files: css/style.css, js/app.js, about.html, images or fonts. index.html becomes the page (previous version kept in history); all other files go to assets/ with their folders kept, and relative links in index.html are rewritten to assets/ automatically, so write normal relative paths like "css/style.css". Text files: put the code in content. Binary files (png, jpg, webp, woff2…): content is base64 and encoding is "base64". Omit index.html to only add or replace files. Limits: 300 files, 10 MB per file, 20 MB in total, the account storage limit. Allowed: html, css, js, json, images (jpg, png, gif, svg, webp, avif, ico), fonts (woff, woff2, ttf, otf), txt, xml, pdf. Use dry_run=true to preview.

Input Schema

NameRequiredDescriptionDefault
siteYesSite id or name, e.g. "my-portfolio" or "my-portfolio.hostilo.page" (from list_sites).
filesYesFiles to publish.
dry_runNoOnly report what would be published; nothing is changed.
clear_assetsNoDelete all current files in assets/ before publishing.
expected_versionNoOptional: the version from get_site. If the site was saved by someone else since then, nothing is published and you get a version_conflict error (get the site again and merge).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / site / description
      Previous value: -"Site id or name, e.g. \"my-portfolio\" or \"my-portfolio.hostilo.app\" (from list_sites)."New value: +"Site id or name, e.g. \"my-portfolio\" or \"my-portfolio.hostilo.page\" (from list_sites)."
  2. Changed1 schema field changed
    • addedInput schema / properties / expected_version
      Added value: +{
+  "description": "Optional: the version from get_site. If the site was saved by someone else since then, nothing is published and you get a version_conflict error (get the site again and merge).",
+  "type": "string"
+}
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true, and the description goes well beyond them: previous index.html is kept in history, other files land in assets/ with folders preserved, and relative links in index.html are rewritten automatically. It also discloses hard limits (300 files, 10 MB/file, 20 MB total, account storage) and the allowed MIME set, which no annotation conveys.

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 with purpose and the create_site alternative, then flows into file placement, encoding, limits and dry_run with almost no filler. The long allowed-extensions enumeration is the one stretch that could be trimmed or left to validation errors.

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 multi-file publish with no output schema, the description covers placement, history retention, link rewriting, encoding, limits, and preview. The only omissions are the destructive clear_assets flag and the expected_version conflict workflow, both of which are documented only in the schema.

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, but the description adds real semantics beyond the schema: the content-vs-encoding rule for binaries ('content is base64 and encoding is "base64"') and the path-rewriting contract that lets callers write normal relative paths. It does not add anything for clear_assets or expected_version, which live only in the schema.

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?

Specific verb ('publishes') plus resource ('several files at once to an existing site'), and it explicitly distinguishes itself from create_site for new sites. The index.html vs assets/ split is spelled out, so the agent knows the tool's exact scope 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 Guidelines5/5

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

Explicit routing: 'use create_site first for a new one', and 'Omit index.html to only add or replace files' tells the agent a meaningful alternate invocation mode. It also names dry_run=true for preview, which is a clear when-to-use signal before a destructive publish.

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

All Hostilo 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