Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Run mock interview prep

mock_interview
Read-onlyIdempotent

Generate a role-specific mock interview plan and questions using verified candidate facts.

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

Input Schema

NameRequiredDescriptionDefault
focusNo
jobIdYes
questionCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description contributes the notable detail that output is grounded in 'verified candidate facts', which hints at factual personalization rather than generic questions. It says nothing about output format, how many questions result, or what happens with an invalid or missing jobId.

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?

A single front-loaded sentence with no filler, and the key qualifier appears early. Its brevity is efficient but tips into under-specification given the undocumented parameters.

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

Completeness2/5

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

With no output schema and 0% parameter description coverage, the description is the only source of invocation guidance, and it omits how 'focus' and 'questionCount' shape the result. For a generative tool whose output shape is undefined, the agent has insufficient context to call it well.

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% across three parameters, so the description carries the full burden and largely fails it. 'Role-specific' loosely implies jobId drives content, but 'focus' and 'questionCount' (with its 4-15 range) are never explained. The agent gets no guidance on what a focus string should contain.

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?

States a specific verb and artifact set: 'Generate a role-specific mock interview plan and questions.' The phrase 'using verified candidate facts' adds a meaningful qualifier about grounding. It does not, however, differentiate from the sibling 'interview_prep', so the agent must infer the boundary.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites (e.g., whether a profile must exist first), and no reference to alternatives such as interview_prep. The only implicit cue is the required jobId, which an agent must read from the schema rather than the description.

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.