Skip to main content
Glama
Sign In
interview-prep-mcp

interview-prep-mcp

by shenmali
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_active_cv_tool

Switch the default CV for interview preparation tools. Provide the CV ID to set which CV other tools use.

Instructions

Switch which CV other tools default to.

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": {
      "cv_id": "<cv_id>"
    },
    "name": "set_active_cv_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
cv_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

The description reveals a side effect (changing defaults globally), but lacks details on reversibility, permissions, or impact on ongoing operations. With no annotations, more behavioral context is needed.

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?

The description is a single concise sentence with no filler. It efficiently conveys the core purpose, though could benefit from additional context without becoming verbose.

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?

Despite low complexity (1 parameter, output schema exists), the description lacks essential details about return values, prerequisites, and parameter meaning. The tool's state-changing nature demands more completeness.

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

Parameters1/5

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

The sole parameter 'cv_id' is not explained in the description. The schema has 0% description coverage, leaving the agent without guidance on what value to provide or where to obtain it.

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 clearly states the action ('Switch') and the resource ('which CV other tools default to'). It uniquely identifies the tool's purpose among siblings, as no other tool sets the active CV.

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?

The description implies usage when one needs to change the default CV for other tools, but it does not provide explicit guidance on when to use versus alternatives, nor does it mention prerequisites or consequences of switching.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools