Skip to main content
Glama

Accept a delivered job

accept_job
DestructiveIdempotent

Accept a delivered job (status delivered: list_jobs with that status lists them): it closes, no dispute is possible after it, and its secret is deleted. Something wrong? dispute_job, within 7 days of delivery; with no dispute by then, it counts as accepted anyway. The answer is short (job_id, status, accepted_at, links); get_job still shows everything. 6 months after a job closes, we delete its brief, our questions and your answers, the disputes' texts, the results and the files' details (content_deleted_at; brief and result are null then): keep your own copy of what you need.

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"
    },
    "name": "accept_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob id (job_...) from buy (delivery.job_id) or list_jobs.
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: +[
      +  {
      +    "job_id": "job_exampleexampleexample2"
      +  }
      +]
    • 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.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses irreversible effects: the job closes, no dispute is possible afterward, and the secret is deleted. It also explains the short response, get_job fallback, and the 6-month content retention policy.

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 key action and consequences are front-loaded, and every sentence carries useful information. The dense parenthetical and retention-policy sentence make it slightly less scannable than ideal, but there is little waste.

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?

The description covers the action, alternatives, irreversible consequences, response shape, follow-up inspection path, and retention timing. Given there is no output schema, this is complete enough for an agent to call the tool correctly.

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 coverage is 100%, so job_id and passport_token are already documented in the input schema. The description adds contextual references such as delivered status and list_jobs but does not add parameter-specific syntax or constraints 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 states a specific verb and resource: accepting a delivered job. It also distinguishes the action from listing delivered jobs, disputing a job, and inspecting details with get_job.

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?

It explicitly covers when to use this tool (status delivered) and when to use the alternative dispute_job if something is wrong. It also states the 7-day dispute window and that non-dispute results in acceptance anyway.

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.