Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Interview prep

interview_prep
Read-onlyIdempotent

Generate role-specific interview preparation without inventing 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": "interview_prep"
  }
}

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 readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description does add a real behavioral constraint -- output must be grounded in candidate facts rather than invented -- which is useful context beyond the structured fields, though it says nothing about length, sources consulted, or what happens when the jobId lacks profile data.

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?

One short, front-loaded sentence with no filler; the grounding constraint is stated up front. It is efficient but so terse that it omits information an agent needs, which is under-specification rather than verbosity.

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, zero parameter documentation, and no explanation of the grounding guarantee's mechanism, the description leaves major gaps for a three-parameter generation tool. An agent cannot tell what focus accepts, how many questions questionCount allows, or what shape the preparation takes.

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 (jobId, focus, questionCount), so the schema itself explains none of them. The description does not mention any parameter, leaving the meaning of focus and the defaults/limits for questionCount entirely undocumented.

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 clear verb and resource ("Generate role-specific interview preparation") plus a scoping qualifier, so an agent knows this produces prep material for a role. It does not, however, distinguish itself from the sibling mock_interview or explain how the two differ.

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?

There is no statement of when to use this tool, when not to, or which sibling to prefer for adjacent tasks such as mock interviews or resume refinement. The agent must infer placement from the name alone.

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.