Skip to main content
Glama

Answer a vacancy's place question

answer_vacancy_place
Idempotent

Record whether the person lives in or can relocate to the place a posting requires, on a vacancy with an 'unverified' eligibility blocker. Yes adds the place to career memory's locations, no is kept as the person's own words; the analyses after it judge the place. This vacancy keeps its verdict: on yes the blocker goes, on no it stays as a 'soft' one. No quota. Errors: not_found (vacancy not theirs), invalid_payload (the vacancy has no open place question).

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": {
      "input": "<input>"
    },
    "name": "answer_vacancy_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Output Schema

NameRequiredDescriptionDefault
saved_asYes'location' — the place joined career memory's locations; 'fact' — the no was kept as the person's own words.
vacancy_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Well beyond the annotations, it discloses cross-domain side effects (yes writes the place into career memory locations), how the 'no' answer is stored (as the person's own words), and the verdict lifecycle (blocker removed on yes, downgraded to 'soft' on no). It also pre-empts rate-limit concerns with 'No quota' and enumerates two error codes. Minor gap: 'soft' blocker is named but not explained, leaving the agent unsure how a soft blocker surfaces later.

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?

Dense and front-loaded: the core action and precondition lead, followed by consequences, quota, and errors in a compact four-sentence block. A few fragments ('No quota.', 'the analyses after it judge the place') are terser than the surrounding prose, but each still carries information.

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?

For a mutation tool with a nested input, output schema present, and non-trivial domain consequences, the description covers preconditions, side effects, state transitions, quota, and error cases. Return values are correctly left to the output schema, and nothing an agent needs to call this correctly appears missing.

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 reported at 0%, so the description carries the burden; it does explain the yes/no meaning of 'holds' and constrains vacancy_id to an 'unverified' blocker vacancy. However, the holds explanation largely restates the schema's own field description, and nothing is added about identifier format or what a valid vacancy_id looks like in practice.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Record') and a precise resource ('whether the person lives in or can relocate to the place a posting requires'), scoped further by the precondition of an 'unverified' eligibility blocker. It is unambiguous what state changes. It never names a sibling (e.g. answer_vacancy_status) to contrast against, so differentiation is implied by domain rather than stated.

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?

Usage context is explicit: the vacancy must have an 'unverified' eligibility blocker and an open place question, and invalid_payload is documented for the case where no open place question exists — an effective when-not signal. No alternative tool is named for other blocker types, so the agent must still infer routing across the broader vacancy toolset.

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.