Skip to main content
Glama

search_mock_interviews

Read-onlyIdempotent

Search EngMock's built-in mock interview catalog by keywords, interview type, difficulty, company, or topic. Returns summaries with question links and practiceUrl, the website's setup page for that interview. Public catalog data; any valid token can use it. To help the user start one, call prepare_mock_interview next.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_mock_interviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based page. Omit for page 1.
queryNoOptional keywords matched against title, description, topics, and companies (case-insensitive, all words must match).
topicNoOptional topic; matches topic labels containing this text case-insensitively.
companyNoOptional company name; matches the catalog's company labels case-insensitively.
pageSizeNoItems per page, 1 to 50. Omit for 20.
difficultyNoOptional exact difficulty label such as Easy, Medium, or Hard (case-insensitive).
interviewTypeNoOptional exact interview type, for example system_design, dsa, ood, or ai_assisted_coding.

Output Schema

NameRequiredDescriptionDefault
pageYes
itemsYes
totalYes
pageSizeYes

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 already declare readOnly/idempotent/no-destructive/openWorld=false, and the description adds meaningful context beyond them: this is public catalog data usable by any valid token, and results include question links and a practiceUrl pointing at the website's setup page. It does not discuss result caps or pagination behavior beyond what the schema states.

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?

Three front-loaded sentences: purpose first, output shape second, next action last. The practiceUrl clause is slightly verbose but contributes genuine meaning; there is no filler.

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 schema exists, so return values need not be detailed, and the brief mention of summaries plus practiceUrl is sufficient. Auth scope and the follow-up tool are covered, leaving only minor gaps like ordering of results or pagination limits.

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 coverage is 100% with per-parameter descriptions for all seven fields, so the schema carries the semantic load. The description only restates the filter categories (keywords, type, difficulty, company, topic) without adding matching behavior or format details beyond what the schema already says.

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 resource ('Search EngMock's built-in mock interview catalog') plus the filter dimensions, so the agent knows exactly what is being queried. It does not explicitly distinguish itself from siblings like list_interviews or search_question_bank, which keeps it just short of a 5.

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?

Gives explicit forward routing: 'To help the user start one, call prepare_mock_interview next,' which tells the agent what to do after a result set is returned. It offers no when-not guidance or comparison against list_interviews or search_question_bank, so the alternative-selection picture is incomplete.

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.

Resources