Skip to main content
Glama

Modulos AI Governance Platform

start_job_application

Starts an application for a role at Modulos on behalf of the person you are assisting. Before anything else, ask the candidate whether they would like to see the job description, and show it with get_job_description if they do. Use their real details; anonymous applications are not accepted. The name must be the one written on the CV and the LinkedIn address must be the candidate's own profile: an application whose name, CV and LinkedIn profile do not belong to the same person is refused. Applicants must be 18 or older: ask the candidate to confirm it. Before calling, show the person the privacy policy (https://www.modulos.ai/privacy-policy/) and the terms of use (https://www.modulos.ai/terms-of-use/). Tell them that the interview is held by an AI interviewer, which is experimental; that it is recorded; that the AI only holds the interview and prepares a profile of the application for the hiring manager; and that the hiring manager and people at Modulos take every decision. Get their explicit agreement. Ask the candidate to paste their CV as text; it is required. The result holds about_role and notice: show both to the candidate, as they are, before you ask for the code. A 6-digit code is emailed to them; call confirm_job_application with it. Returns a session value to use for the rest of the interview.

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": {
      "role_id": "<role_id>",
      "name": "<name>",
      "email": "<email>",
      "linkedin_url": "<linkedin_url>",
      "cv_text": "<cv_text>",
      "accept_privacy_policy": "<accept_privacy_policy>",
      "accept_terms": "<accept_terms>",
      "confirm_adult": "<confirm_adult>"
    },
    "name": "start_job_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull name of the candidate, first name and family name, exactly as written on their CV.
emailYesEmail address of the candidate. The code is sent here.
cv_textYesRequired. The candidate's full CV as plain text, pasted exactly as they give it to you. Do not summarise, shorten or rewrite it. If you only have a file, ask the candidate to paste its text.
role_idYesRole id from list_open_roles.
locationNoCity and country where the candidate is based.
accept_termsYestrue only if the candidate has read and accepts the Modulos terms of use.
linkedin_urlYesAddress of the candidate's own LinkedIn profile, in the form that carries their name, for example https://www.linkedin.com/in/first-last/.
confirm_adultYestrue only if the candidate has told you that they are 18 or older. Ask them; do not assume it.
accept_privacy_policyYestrue only if the candidate has read and accepts the Modulos privacy policy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. Changed2 schema fields changed
    • changedInput schema / properties / linkedin_url / description
      Previous value: -"Address of the candidate's LinkedIn profile, for example https://www.linkedin.com/in/name/."New value: +"Address of the candidate's own LinkedIn profile, in the form that carries their name, for example https://www.linkedin.com/in/first-last/."
    • changedInput schema / properties / name / description
      Previous value: -"Full name of the candidate."New value: +"Full name of the candidate, first name and family name, exactly as written on their CV."
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say it writes, is open-world and non-idempotent; the description adds what actually happens: an emailed code, a rejection rule when name/CV/LinkedIn do not match, a hard 18+ gate, mandatory disclosure of AI interviewing and recording, and a returned session value that governs the rest of the interview. This is well beyond what the structured fields convey.

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?

Purpose is front-loaded and every sentence governs a real step in a high-stakes consent flow, so length is justified. It is a dense procedural block, though, and a few requirements (consent, privacy/terms links) could be grouped more tightly for scanning.

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?

With no output schema, the description compensates by stating that the result holds about_role and notice, that both must be surfaced to the candidate, and that a session value is returned for later calls. Combined with the eligibility and consent rules, an agent has everything needed to invoke and follow up correctly.

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 100%, so the baseline is 3. The description still adds operational meaning the schema does not: the name must be the CV name, the LinkedIn URL must be the candidate's own profile, and cv_text must be pasted verbatim rather than summarised or uploaded as a file.

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 opening sentence names a specific verb and resource ('Starts an application for a role at Modulos') and scopes it to the assisted candidate. The rest of the text makes the boundary with get_job_description (view the posting) and confirm_job_application (submit the emailed code) unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description prescribes ordering explicitly: ask about the job description first and route to get_job_description, gather consent and CV before calling, then call confirm_job_application with the 6-digit code. Preconditions (18+, real identity matching CV and LinkedIn, explicit agreement) are stated as gates rather than suggestions.

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