Skip to main content
Glama

Answer our team's question about a job

answer_job_question

Answer our team's open question on a job (status needs_info; get_job shows it as question). Leave out question_id to answer the open one. The job goes back to work, and due_at moves on by the working time it waited. A login they ask for goes in secret (write-only), never in answer.

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": {
      "answer": "Mobile matters most.",
      "job_id": "job_exampleexampleexample2",
      "question_id": "jq_exampleexampleexample2"
    },
    "name": "answer_job_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
answerYesYour answer, plain text.
job_idYesJob id (job_...) from buy (delivery.job_id) or list_jobs.
secretNoWrite-only: a test login or key the team asked for, only while the job holds none (an answer never replaces one).
question_idNoquestion.question_id from get_job.
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. Changed3 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "answer": "Mobile matters most.",
      +    "job_id": "job_exampleexampleexample2",
      +    "question_id": "jq_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."
    • changedInput schema / properties / secret / description
      Previous value: -"Write-only: a test login or key the team asked for."New value: +"Write-only: a test login or key the team asked for, only while the job holds none (an answer never replaces one)."
  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.1/5.0
Behavior4/5

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

Adds real side-effect disclosure beyond the annotations: the job resumes work and due_at is extended by the working time it waited, and a requested login must go in secret because it is write-only and never set in answer. Annotations only flag non-readOnly, non-idempotent, open-world; the description explains the consequence. It stops short of stating failure modes or what a rejected answer looks like.

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?

Four short sentences, front-loaded with the action and the state gate before the side effects. Parentheticals are dense but each carries information; nothing is filler.

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 carries the burden of explaining outcomes, and it does state what happens after success (job back to work, deadline extended). It leaves the response payload and error conditions unstated, so a caller cannot predict what it gets back.

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 baseline is 3. The description does add genuine meaning on top: question_id is optional and omitting it targets the open question, and secret is only accepted while the job holds none (an answer never replaces an existing one). Helpful, but mostly restates constraints the schema already encodes.

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?

Names a specific verb and resource (answer a job's question) and pins the exact precondition: the job must be in status needs_info, visible via get_job as a question. That is enough for an agent to distinguish this from get_job, ask_human, or accept_job without opening a 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?

Gives the operative condition (job in needs_info / shown as question by get_job) and the rule for the optional question_id: omit it to answer the open one. It never names an explicit exclusion or a competing tool to prefer, so it falls just short of full when/when-not guidance.

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.