Skip to main content
Glama

Dispute items of a delivered job

dispute_job

Dispute items of a delivered job (ids from get_job's disputable_items: bugs, findings, rows, translation lines l1, l2 ...) or, without item_ids, the whole result, within 7 days of delivery. Our staff answer within 48 hours with proof, store credit, or a corrected version of the result (signed and delivered again; you may accept it or dispute it again); no answer in time is a credit. Nothing wrong: accept_job instead.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_id": "job_exampleexampleexample2",
      "reason": "Line 2 is not translated.",
      "item_ids": [
        "l2"
      ]
    },
    "name": "dispute_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob id (job_...) from buy (delivery.job_id) or list_jobs.
reasonYesWhat is wrong, for our staff (plain text).
item_idsNoItems you dispute; leave out to dispute the whole result.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "item_ids": [
      +      "l2"
      +    ],
      +    "job_id": "job_exampleexampleexample2",
      +    "reason": "Line 2 is not translated."
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the mutation profile (readOnly=false, destructive=false, idempotent=false, openWorld=true); the description goes well beyond that with the 7-day window, the 48-hour staff SLA, the three possible resolutions (proof, store credit, corrected version), the re-dispute cycle, and the fallback credit if no answer arrives. That is exactly the outcome and timing context an agent needs before committing a dispute.

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 main action is front-loaded and every clause carries information (scope, window, SLA, outcomes, alternative). The heavy nested parentheses and semicolon chaining make the SLA sentence harder to parse than necessary, costing some readability.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description still tells the agent what comes back from a dispute (proof, credit, or a corrected and re-delivered result) and what happens on timeout. Combined with the timing constraints, nothing essential for a correct call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds real meaning by explaining where item_ids come from and what they look like (bugs, findings, rows, translation lines l1, l2). It also restates the omit-to-dispute-everything semantics, which the schema already covers, so it stops short of a 5.

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?

Specific verb+resource ("Dispute items of a delivered job") with immediate scope clarification: item-level disputes use ids from get_job's disputable_items, while omitting item_ids disputes the whole result. It also names the neighboring path ("Nothing wrong: accept_job instead"), so an agent can distinguish it from accept_job and get_job without opening schemas.

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?

Gives an explicit eligibility window ("within 7 days of delivery"), an explicit exclusion ("Nothing wrong: accept_job instead"), and the item-level vs whole-result choice. It also names the upstream source of ids (get_job's disputable_items), which is the practical precondition for calling it.

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.