Skip to main content
Glama

add_version

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Add your own staged private upload as the current version of your draft. Withdraw proposed builds to drafts first. Never proposes it.

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": {
      "change": "<change>",
      "uploadId": "<uploadId>"
    },
    "name": "add_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
changeYesThe change's id from my_changes (not its title).
uploadIdYesYour staged private upload's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does useful work by disclosing the auth requirement (OAuth connection or Authorization: Bearer API key) and the draft-withdrawal prerequisite, and it makes clear this mutates the draft's current version. It does not cover failure modes, whether the previous version is retained/restorable, or what happens if the upload id is stale.

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 short sentences, none padded. The auth note leads, which is slightly awkward for a purpose-driven read, but the core statement and the prerequisite each earn their place.

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 two-parameter mutation with no annotations and no output schema, the description covers auth, a hard ordering constraint, and the publish/non-publish boundary. Only the post-call state (what the draft version looks like, whether prior versions persist) is left implicit, which is a modest gap rather than a blocking one.

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 description coverage is 100%, so both parameters are already documented as ids from my_changes and the staged upload respectively. The description reinforces ownership scope ('your own staged private upload', 'your draft') but adds no format or lookup detail beyond the schema, so 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 and resource: add a staged private upload as the current version of the caller's draft. The closing 'Never proposes it' explicitly disambiguates it from the submission/publish siblings, so an agent can tell what this tool is not without opening another schema.

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 a concrete precondition ('Withdraw proposed builds to drafts first') that governs when this tool can be invoked, plus the negative guidance that it never proposes/publishes. It stops short of naming which sibling to call when the user actually wants to submit a build, leaving that inference to the agent.

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