Skip to main content
Glama

Youth4work (public, no sign-in)

Search mock tests

search_mock_tests
Read-onlyIdempotent

Exam preparation on Youth4work Prep (start free: a free account gets 50 practice questions per exam category and a free sample mock test where available; a paid pack unlocks every test, see the result note): finds exams (e.g. "SSC CGL", "IBPS PO", "RRB NTPC", "CAT") by name and/or category (e.g. "Government Jobs", "Bank", "Placement Papers"), most popular first, each with its exam page url and up to 5 mock tests (questions, minutes, url).

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_tests"
  }
}

Input Schema

NameRequiredDescriptionDefault
examNoExam name or part of it, e.g. "SSC", "IBPS PO"
pageNoResult page, 20 per page (default 1)
categoryNoCategory, e.g. "Government Jobs"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: the free tier caps at 50 practice questions per exam category with only a sample mock test where available, and a paid pack is required for full access — important for interpreting truncated results. It stops short of describing error or empty-result behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence that front-loads the action and result shape, which is good structure. But a long monetization parenthetical ("start free ... see the result note") sits between the verb and the actual behavior, diluting the core message and reading more like promotional copy than tool documentation.

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?

For a three-optional-parameter search tool with no output schema, the description is nearly sufficient: it explains matching inputs, sort order, paging behavior via the schema, and the per-exam result contents. The main gap is the absence of any guidance on how this relates to get_mock_test or the other search_* tools.

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%, so the schema already documents exam, category and page (20 per page, default 1). The description reinforces the parameters with concrete example values that match the schema's own examples but adds no new semantics such as partial-match or case-sensitivity rules. Baseline 3 is appropriate.

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 ("finds exams ... by name and/or category") and even enumerates the return payload: exam page url plus up to 5 mock tests with questions, minutes and url. It does not explicitly name the sibling it differs from (get_mock_test for a single test), so an agent must infer that boundary from the "up to 5 mock tests" summary shape.

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 by the examples given ("SSC CGL", "IBPS PO", "Government Jobs") and by "most popular first", so an agent can tell this is a discovery/browse call. However, there is no explicit when-to-use/when-not statement and no pointer to get_mock_test for full test detail or to the other search_* siblings for different resource types.

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