Skip to main content
Glama

Appeal my quarantine

pipeline_appeal
Idempotent

Appeal your own quarantine. This is the one write a quarantined agent may make: everything else is refused until a person releases you. It answers with the three ceilings as they stand for you right now, so you can see which number fired. One appeal per quarantine; filing it again changes nothing. A person reads every appeal, and the person behind you was mailed the moment you were quarantined.

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": {
      "reason": "<reason>"
    },
    "name": "pipeline_appeal"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only give the write/idempotent/no-open-world safety profile; the description adds the material facts an agent can't get from them: the return content (the three ceilings as they stand now, so you can see which number fired), the human review path, the one-per-quarantine limit, and the side effect that the agent behind you was already mailed. Disclosure of downstream notification is exactly the kind of consequence an agent needs before mutating state.

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?

Front-loaded with the action and the constraint, then consequences. Every sentence carries information, though "everything else is refused until a person releases you" and "a person reads every appeal" partially overlap on the human-review point, costing a little tightness.

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?

With no output schema, the description usefully says what comes back (the three ceilings and which one fired) and notes the notification side effect. It stops short of saying how or when the agent learns the outcome of the appeal, which is the remaining piece of context for a blocked agent.

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?

There is one parameter, `reason`, and schema description coverage is 0% — only minLength 8 / maxLength 2000 constraints appear in the schema. The description says nothing about what a reason should contain or how it is judged by the human reader, so it fails to compensate for the coverage gap on the only input that matters.

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 ("Appeal your own quarantine") and immediately scopes it: the single write a quarantined agent may make, with everything else refused. That, plus the sibling names all being pipeline_* actions, makes it unmistakable which tool to reach for when quarantined.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames the triggering condition (you are quarantined), the exclusion (everything else is refused until a person releases you), and the repeat-use rule (one appeal per quarantine; filing it again changes nothing). An agent knows both when to call it and when calling it is pointless.

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