Skip to main content
Glama

Modulos AI Governance Platform

confirm_job_application

Idempotent

Confirms the 6-digit code that was emailed to the candidate, which opens the interview. Ask the candidate for the code; do not guess it. The result holds the interviewer's first words and first question: show them to the candidate exactly as they are, with nothing added.

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": {
      "session": "<session>",
      "code": "<code>"
    },
    "name": "confirm_job_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe 6-digit code from the email.
sessionYesThe session value returned by start_job_application. Keep it for the whole interview and do not show it to anyone else.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag readOnlyHint=false and idempotentHint=true, and the description adds real context beyond them: the code arrives by email, confirming opens the interview, and the result carries the interviewer's opening words and first question. Given there is no output schema, describing the return content and the verbatim-display requirement is exactly the kind of disclosure that earns credit. It does not cover failure modes such as an expired or incorrect code.

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?

Two tight sentences, front-loaded with the action and its effect, followed by the two behavioral constraints (do not guess; display the result verbatim). Nothing is padded or repeated from the schema.

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?

For a two-parameter, no-output-schema tool, the description covers the input source, the effect of success, and how to handle the returned text, which is the core of what an agent needs. It stops short of describing what happens when the code is wrong or the session is stale, a real gap for a state-changing call.

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 description coverage is 100%, with both code and session already documented in the schema, including the session's provenance from start_job_application. The description reinforces that the code was emailed to the candidate but adds no new syntax or format meaning, so the baseline 3 applies.

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?

States a specific verb and resource (confirm the 6-digit code) plus the concrete effect: it opens the interview. The flow relationship to start_job_application is implicit in the session parameter but the action itself is unambiguous, so an agent can distinguish this from start_job_application or talk_to_interviewer.

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?

"Ask the candidate for the code; do not guess it" gives clear operational guidance on how the input must be obtained, which is unusual and valuable. It lacks an explicit statement of when in the sequence to call it relative to siblings, but the dependency on a code emailed after start_job_application makes the ordering clear enough.

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