Skip to main content
Glama

TrueInterview

Skip a job

skip_job
Idempotent

Hide a role from the board and recommendations, as the board's "Not interested" does. why company, role, seniority, skill (with skill) or eligibility also hides roles like it; rule says what was written. undo: true shows it again. Only on the candidate's word.

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": {
      "job_id": "<job_id>"
    },
    "name": "skip_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
whyNonot_relevant
undoNo
skillNoWith why "skill", e.g. "Java".
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare idempotent, non-destructive, non-readOnly; the description adds behavior they cannot express — that certain `why` values (company, role, seniority, skill, eligibility) suppress *other* similar roles, not just the one ID, and that undo:true reverses the hide. That is exactly the non-obvious side-effect disclosure an agent needs before invoking.

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

Conciseness3/5

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

It is short and front-loads the core effect, but the middle sentence is telegraphic and grammatically broken ('why company, role, seniority, skill (with skill) or eligibility also hides roles like it; rule says what was written'), forcing the reader to re-parse. Density is bought at the cost of clarity.

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

Completeness3/5

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

For a mutation hiding user-visible state with no output schema, the description covers the essential facts: what is affected, that similar roles may also be hidden, and how to reverse it. It omits the return value, whether the effect persists across searches, and any scope limits, leaving the agent with moderate but not full confidence.

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 only 25% and the `why` enum carries no per-value descriptions, so the description does real work: it explains which `why` values trigger broader suppression, links `skill` to why='skill', and explains `undo`. It is not complete — 'rule says what was written' is cryptic and job_id scope is left implicit — but it compensates substantially for the low coverage.

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 opening clause names a specific verb and effect: 'Hide a role from the board and recommendations,' and anchors it to a concrete UI analogue ('as the board's "Not interested" does'). That is enough to distinguish it from read-oriented siblings like get_job or recommend_jobs, though no sibling is named explicitly.

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 closing rule 'Only on the candidate's word' is an explicit gating condition that tells the agent not to skip autonomously, and the 'Not interested' analogy frames the situation. It stops short of naming alternatives (e.g., searching or saving a note about the role) or stating when skipping is inappropriate.

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.

Resources