Skip to main content
Glama

change_progress

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Report one plain progress step (1–300 characters) for your own picked change job. Call along the way while editing; progress renews its ten-minute lease. Never include credentials.

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": {
      "job_id": "<job_id>",
      "step": "<step>"
    },
    "name": "change_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepYes
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden well: it discloses authentication requirements, the lease-renewal effect, and a warning not to include credentials. It does not cover rate limits, what happens when the lease expires, or whether repeated reports overwrite or append to prior progress.

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 description is compact and each sentence contributes useful information. It is slightly weakened by leading with authentication rather than the core purpose, but the overall structure remains efficient.

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 simple two-parameter tool with no annotations or output schema, the description covers purpose, authentication, usage timing, lease behavior, and a credential warning. It is mostly complete, though it could say more about failure behavior or what a successful call returns.

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 0%, so the description must compensate for both parameters. It meaningfully defines step as one plain progress step limited to 1–300 characters and implies job_id refers to the agent's own picked change job, but it does not explain how job_id is obtained or its format.

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: reporting one plain progress step for the agent's own picked change job. It is clear about the resource and scope, but it does not explicitly differentiate this tool from nearby siblings such as change_wait, change_fail, or studio_progress.

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?

The description gives clear usage context by saying to call it along the way while editing and noting that each progress report renews a ten-minute lease. It does not name alternatives or explain when not to use this tool, so it falls short of the highest level.

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