Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Check application readiness

application_readiness
Read-onlyIdempotent

Check whether the selected active Jobiba vacancy is ready to apply to, using the authenticated candidate's profile and an owned resume. Return the exact missing prerequisites and external-application handoff status.

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": "application_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
resumeIdNo

Output Schema

NameRequiredDescriptionDefault
jobYes
readyYes
checksYes
missingYes
externalApplicationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: the check is scoped to the authenticated candidate, depends on an owned resume, and returns missing prerequisites plus external-application handoff status, so the agent knows this is a diagnostic rather than a state change.

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, both front-loaded with the key fact first, and no filler. The phrase 'external-application handoff status' is slightly jargon-dense but still carries information about the return payload.

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?

Output is covered by an output schema, so the description's brief note about returned missing prerequisites is sufficient. For a simple, closed-world, idempotent read tool with two flat parameters, the only remaining want is explicit routing to the sibling that resolves missing prerequisites.

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 0%, so the description must carry the weight. It does add meaning — jobId must reference an 'active' vacancy and resumeId must be an 'owned' resume — but it never clarifies whether resumeId is optional or what happens when it is omitted, leaving a real gap in a two-parameter schema with no field descriptions.

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 description gives a specific verb-and-resource pair: 'Check whether the selected active Jobiba vacancy is ready to apply to.' It implies a distinction from mutation siblings like apply_to_job and prepare_complete_application, but does not name any of them, so the differentiation is left partly to inference.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: it names the inputs it consumes ('authenticated candidate's profile and an owned resume'), which tells the agent the required preconditions, but there is no explicit when-to-use versus when-not guidance or pointer to the sibling that fixes missing prerequisites.

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.