Skip to main content
Glama

deed.page

by page.deed
OverviewDiscussionsAdmin

Plan a large upload

plan_upload

Accepts a file manifest and returns which hashes are already stored, a direct upload URL for each missing hash, and a session id. Inputs: files as {path, sha256, size, content_type?}, and optional slug, spa, merge, ttl_seconds, expected_version, via, and token. Applies when the files are larger than about 4 MB, or when each sha256 is already known. Does not publish by itself. Per-site size limits are unchanged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spaNo
viaNoOptional label stored with the publish. At most 80 characters. An IP address, a URL, or an email address is not stored. A non-empty value replaces the X-Via header.
slugNoExact slug, or omit for a random one.
filesYesManifest entries. sha256 is 64 lowercase hex characters. size is the byte length.
mergeNoOverlay these paths on the live site.
tokenNoBearer token returned by your first publish (deed_tok_...). Optional if the MCP client sends Authorization: Bearer.
ttl_secondsNo
expected_versionNoLive version this upload must match, such as "v3".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / via
      Added value: +{
+  "description": "Optional label stored with the publish. At most 80 characters. An IP address, a URL, or an email address is not stored. A non-empty value replaces the X-Via header.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / expected_version / description
      Previous value: -"Live version this finalize must match, such as \"v3\"."New value: +"Live version this upload must match, such as \"v3\"."
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=true. The description adds real context beyond that: it is a preparatory step that 'does not publish by itself', it returns a session id for a later finalize, and it discloses the token/bearer auth path. It does not cover TTL/expiry semantics or rate limits.

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-loads the most decision-relevant fact (what it returns) before the input list and applicability rules. Dense but every clause carries information; the input enumeration is somewhat list-heavy but earns its place given 8 parameters.

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?

With no output schema, the description correctly supplies the return shape (stored hashes, upload URLs, session id), plus the trigger condition and the 'does not publish' caveat, which is the key mental model for a two-step upload. Remaining gaps are minor: what to do with the session id / which sibling finalizes, and TTL behavior.

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 75% and the strong per-parameter docs (via, slug, merge, token, expected_version, files item shape) already live in the schema. The description only re-lists parameter names and the manifest entry fields, adding little semantic meaning beyond the structured data. Baseline 3 applies.

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+resource (plan a large upload) and, unusually, enumerates the return payload (already-stored hashes, per-hash upload URLs, session id). The phrase 'Does not publish by itself' implicitly separates it from finalize_upload/publish_site, so an agent can place it in the upload flow without opening the sibling schemas.

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 an explicit applicability condition ('files larger than about 4 MB, or when each sha256 is already known'), which tells the agent when this tool is the right entry point rather than a single-shot publish. It stops short of naming the alternative path for small/unknown-hash uploads, so the routing is implied rather than stated.

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

All deed.page 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