Skip to main content
Glama

start_change

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Start your own private change from a staged private upload and a description. 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": {
      "slug": "<slug>",
      "text": "<text>",
      "uploadId": "<uploadId>"
    },
    "name": "start_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
textYes
uploadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the auth requirement and the important negative behavior that the change is never proposed/submitted for review. It omits other behavioral facts an agent would want: that this is a state mutation, what happens to the staged upload afterward, and what identifier is returned.

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?

Two sentences with no filler, and the auth prerequisite is front-loaded before the action. The brevity is efficient, though the clipped 'Never proposes it' phrasing reads more like a fragment than a clear constraint.

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 three-required-parameter mutation with no annotations and no output schema, so the description should explain the slug, the relationship to a staged upload, and the success outcome. It covers authentication and one negative behavior but leaves the core parameter and the resulting change state undocumented.

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?

Schema description coverage is 0% across three required parameters, so the description must compensate. It only loosely maps 'a staged private upload' to uploadId and 'a description' to text (which is capped at 2000 chars, a limit not mentioned), and the required 'slug' parameter is entirely unexplained — an agent cannot tell whether it must pre-exist, must be new, or how it is formatted.

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?

States a specific verb and resource: 'Start your own private change from a staged private upload and a description,' which tells an agent this creates a change record from a prior upload. 'Never proposes it' hints at the distinction from a proposal/submission flow, though the phrase is terse and does not name the sibling it contrasts with.

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?

Supplies an authentication prerequisite (OAuth connection or Authorization: Bearer API key), which is real usage context, and 'your own private' plus 'never proposes it' imply this is for personal, non-submitting changes. It stops short of naming when to use this instead of add_version, my_changes, or prepare_submission.

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