Skip to main content
Glama
Sign In

ResumeQuick

by app.resumequick
OverviewDiscussionsAdmin

Answer a vacancy's status question

answer_vacancy_status
Idempotent

Record whether the person has the status a posting requires, on a vacancy whose verdict_category is 'confirm_status'. The answer goes into career memory and settles this vacancy: with the status the blocker goes and the verdict follows the match, without it the verdict is 'not_eligible'. match_percentage does not change. No quota. Errors: not_found (vacancy not theirs), invalid_payload (the vacancy has no open status 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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes

Output Schema

NameRequiredDescriptionDefault
vacancy_idYes
verdict_categoryYesThe verdict the answer comes to; match_percentage does not change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: the answer is written to career memory, settles the vacancy, determines the verdict based on the match, and leaves match_percentage unchanged. It also discloses that no quota is used and names the expected errors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and applicability condition, followed by consequences and errors. Despite being dense, every sentence contributes useful information for correct invocation.

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 annotations and an output schema, the description covers the necessary context: when it applies, what it changes, what remains unchanged, and which errors to expect. Return-value details can be deferred to the output schema.

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?

Although the reported schema description coverage is low, the description clarifies the meaning of both inputs: 'holds' is tied to whether the person has the required status, and 'vacancy_id' must reference a vacancy with verdict_category 'confirm_status'. It does not add syntax details, but it compensates semantically for the key parameters.

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 action and resource: record whether the person has a required status for a vacancy. It also narrows the applicability to vacancies whose verdict_category is 'confirm_status', so the agent can distinguish this from adjacent vacancy-status tools.

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?

The trigger condition is explicit: only use this on a vacancy with verdict_category 'confirm_status'. It also explains the invalid_payload condition when there is no open status question, though it does not explicitly name the sibling tool to use for other vacancy status updates.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ResumeQuick toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources