Skip to main content
Glama

Retain project source

begin_project_source
Idempotent

Creates a private upload reservation for matching original development source when source backup is enabled for the project. Reports whether the source was saved.

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>",
      "deployment_id": "<deployment_id>",
      "size_bytes": "<size_bytes>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "begin_project_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesExact stable project ID. Resolve it first. Never invent an update target.
size_bytesYes
deployment_idYes
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already establish that this is a non-destructive, idempotent write with no open-world access. The description adds useful context about the prerequisite backup setting and that it reports whether source was saved, but it leaves unclear what the upload reservation entails, whether it expires, and what failure modes exist.

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 definition is short and front-loads the core operation and condition. The phrase 'private upload reservation' is somewhat jargon-heavy, but there is no obvious filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a write-style upload reservation tool with no output schema and only half of its parameters described in the schema. The description mentions the backup prerequisite and a vague saved/not-saved report but does not explain the upload flow, reservation lifecycle, or response behavior sufficiently for the tool's complexity.

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

Parameters2/5

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

The description adds essentially no meaning for the four required parameters. With only 50% schema description coverage, it should compensate for undocumented fields such as deployment_id and size_bytes, but it does not explain their role in the reservation.

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?

The description states a specific action and resource: creating a private upload reservation for original development source. It also includes the enabling condition, but it does not explicitly distinguish this tool from related deployment or project tools.

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?

It gives one conditional cue, that source backup must be enabled for the project, which implies when the tool is applicable. However, it does not say when not to use it, what to do if backup is disabled, or name any alternative tool.

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