Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Prepare complete application

prepare_complete_application
Destructive

Builds a reviewable application package for an active vacancy: evidence-based match, readiness gaps, a tailored saved resume (with keyword coverage and a change list) and a cover-letter draft. It does not submit anything or contact any employer.

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": {
      "jobId": "<jobId>"
    },
    "name": "prepare_complete_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNo
jobIdYes
resumeIdNo
instructionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, so the description's clarification that it 'does not submit anything or contact any employer' adds valuable scoping and is consistent with the write profile (it saves a resume). It does not explain what gets overwritten or created when resumeId is supplied, which would be useful given destructiveHint=true.

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?

Two sentences, front-loaded with what is produced and followed by the key non-action boundary. The parenthetical enumeration is dense but earns its place by naming concrete deliverables; a slight cost is the long noun stack in the first sentence.

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?

The output description is good, and no output schema exists so describing deliverables is appropriate. But with no annotations covered parameters, 0% schema coverage, and no output schema, the definition leaves an agent unsure how tone/resumeId/instructions change behavior or what a 'readiness gap' result looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, but it only implies jobId (active vacancy) and hints at a saved resume. It says nothing about tone, resumeId, or instructions, leaving three of four parameters unexplained in both schema and description.

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 names a specific verb ('Builds') and resource ('a reviewable application package for an active vacancy') and enumerates outputs: match evidence, readiness gaps, tailored saved resume with keyword coverage and change list, and a cover-letter draft. This distinguishes it from siblings like build_or_refine_resume or generate_cover_letter, which produce individual artifacts, by making clear this is the bundled end-to-end orchestrator.

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?

It gives clear context ('for an active vacancy') and a critical exclusion: 'It does not submit anything or contact any employer,' which routes submission intent to apply_to_job. However, it does not explicitly say when to prefer this composite over calling the individual sibling tools, nor mention prerequisites such as requiring a resumeId.

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.