Skip to main content
Glama

Youth4work (public, no sign-in)

Get mock test

get_mock_test
Read-onlyIdempotent

Details of one mock test by id (from search_mock_tests): exam, sections, number of questions, duration, marking, the instructions page url and the url that starts the test (needs a free Youth4work sign-in; the note says what is free and what needs a Prep pack).

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": {
      "mock_test_id": "<mock_test_id>"
    },
    "name": "get_mock_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
mock_test_idYesMock test id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint and destructiveHint, so the bar is lower, yet the description adds genuinely new context: the start-test URL requires a free Youth4work sign-in and the instructions note explains what is free versus what requires a Prep pack. It also discloses the shape of the payload rather than leaving the agent to guess.

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 front-loaded sentence that packs the return fields and the auth caveat without filler. The nested parenthetical about sign-in and Prep pack makes it slightly run-on, but every clause carries information.

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

Completeness5/5

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

There is no output schema, so naming the returned fields is necessary and done here, and the authentication/free-versus-paid caveat covers the main surprise an agent would hit on invocation. Nothing material for correct calling is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds provenance the schema lacks by stating the id comes from search_mock_tests, which tells the agent where a valid value originates rather than that any positive integer works.

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?

States a specific verb and resource ("Details of one mock test by id") and enumerates exactly what is returned — exam, sections, question count, duration, marking, and two URLs. The parenthetical "(from search_mock_tests)" distinguishes it from the sibling search tool without opening either schema.

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?

The reference to search_mock_tests as the id source tells the agent this is the follow-up call after a search, which is the key routing decision for this pair. It does not state exclusions or when not to call it, but the retrieval context is clear.

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