Skip to main content
Glama

Undo a pass on a job listing

unpassJob
Idempotent

Undo passJob, so the listing shows up in searchJobs again.

Undoing a listing that was never passed returns not_passed and changes nothing.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "jobId": "<jobId>"
    },
    "name": "unpassJob"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe jobId that was passed with passJob.

Output Schema

NameRequiredDescriptionDefault
jobIdYes
outcomeYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, so the bar is lower. The description still adds real value: it discloses the visible state change, the no-op edge case with its 'not_passed' return signal, and a data-recording notice — none of which appear in the annotations.

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, front-loaded with the core action and effect before the edge case. The privacy sentence is boilerplate but brief and arguably compliance-required; nothing else is wasted.

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?

The tool is simple (one required param) and an output schema exists, so return values need not be explained. The description covers the action, its effect, and the failure path, leaving only sibling disambiguation against 'undoPass' unaddressed.

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?

With a single parameter at 100% schema coverage, the schema already explains that jobId is the ID previously passed to passJob. The description reinforces that framing ('a listing that was never passed') but adds no syntax, format, or sourcing detail beyond the schema.

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?

The description names a specific verb+resource pair ('Undo passJob') and states the observable effect ('the listing shows up in searchJobs again'), which ties it directly to two sibling tools. An agent can distinguish it from a generic undo without reading the 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?

It clearly frames the tool as the inverse of passJob, which gives strong when-to-use context. It does not address the confusingly similar sibling 'undoPass', so an agent must infer from the 'listing'/'passJob' wording that this tool is the job-scoped variant.

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