Skip to main content
Glama

change_fail

Needs sign-in (connect this server with OAuth, or pass an API key as the Authorization: Bearer header). Finish your own picked change job with a plain reason (up to 300 characters) when it cannot be built. 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>",
      "reason": "<reason>"
    },
    "name": "change_fail"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
reasonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 behavioral burden. It helpfully discloses authentication requirements and warns against including credentials, but it does not explain what happens to the job after failure, whether the action is reversible, or any downstream effects.

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 adds useful information. Authentication appears first rather than the core action, which slightly weakens front-loading, but overall it is efficient.

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

Completeness3/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 or output schema, the description covers auth, ownership, usage condition, and reason length. It is still missing key context such as the job status transition and where job_id comes from.

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. It clarifies that the job must be one the caller picked and that the reason should be plain text up to 300 characters, but it does not explain the expected job_id format or where to obtain it.

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 clearly states the action: finish a picked change job with a reason when it cannot be built. It distinguishes ownership ("your own picked") and failure context, but does not explicitly contrast with related tools such as studio_fail.

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?

It gives a clear condition for use: when your own picked change job cannot be built. It does not list exclusions or name alternative tools, which keeps it from a 5.

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