Skip to main content
Glama
art22017

СДАМ ГИА MCP Server

by art22017

Get Test Problems

sdamgia_get_test
Read-onlyIdempotent

Retrieve all problem identifiers for a specific exam variant to access its curated problem set for timed practice or test analysis.

Instructions

Retrieves all problem identifiers that comprise a specific test or examination variant.

PURPOSE: Fetches the complete list of problem IDs that make up a predefined test or exam variant. Tests are curated collections of problems designed to simulate actual exam conditions or assess specific skill sets.

WHEN TO USE:

  • Use when you need to see all problems in a specific test variant or exam

  • Use when working with practice tests or mock exams

  • Use when you need the complete problem set for timed test simulations

  • Use when analyzing test composition or difficulty distribution

  • Use when preparing for real exams by reviewing official test variants

  • Essential for accessing complete, ready-made problem collections

KEY PARAMETERS:

  • subject (required): The subject identifier (e.g., 'ege', 'oge', 'math')

  • test_id (required): Unique identifier for the specific test/variant to retrieve

  • response_format (optional): Output format - 'json' for structured data, 'markdown' for formatted text (default: 'json')

PARAMETER CONSTRAINTS:

  • test_id must be a valid, existing test identifier for the specified subject

  • Invalid test IDs will result in errors or empty results

  • Test IDs are typically numeric but may include alphanumeric codes

  • Not all test IDs may be publicly accessible or available

  • Test availability may vary by subject and time period

RESPONSE FORMAT: Returns an array of problem ID strings/numbers:

  • Each ID represents a problem in the test sequence

  • IDs are returned in test order (first problem to last)

  • Tests typically contain 5-25 problems depending on exam type

  • Total count of problems is included in response metadata

  • Problems are already curated and balanced by difficulty/topic

IMPORTANT NOTES:

  • This tool ONLY returns problem IDs, NOT problem content, statements, or solutions

  • Test IDs are different from category IDs - they reference specific exam variants

  • Test composition is fixed and determined by test creators

  • The same problem may appear in multiple tests

  • Tests are designed to be completed within specific time limits

  • Some tests may include special instructions or sections not visible in ID list

  • Test availability may be limited by region, year, or exam board

DISTINCTION FROM CATEGORY QUERIES: Unlike sdamgia_get_category_problems which fetches all problems from a topic, this tool fetches problems from a specific, curated test variant. Tests are pre-assembled problem sets, while categories are thematic collections.

EXAMPLE WORKFLOW:

  1. Obtain test_id from external source (e.g., 'ege-2023-variant-123' or numeric ID)

  2. Call sdamgia_get_test(subject='ege', test_id='12345')

  3. Receive ordered array: [5001, 5002, 5003, 5004, 5005, ...]

  4. Use individual problem IDs with sdamgia_get_problem for full content

  5. Present problems in order to simulate actual exam experience

TYPICAL USE CASES:

  • "Get all problems from EGE 2023 variant 15"

  • "Show me the complete problem list for OGE practice test 7"

  • "Retrieve all problems in diagnostic test variant 42"

  • "What problems are included in the final exam simulation test?"

  • "Fetch the problem IDs for yesterday's practice test"

PRACTICAL APPLICATIONS:

  • Creating timed practice sessions with real exam variants

  • Analyzing difficulty patterns in official tests

  • Comparing problem distributions across different test years

  • Building test preparation schedules using official variants

  • Reviewing complete test content before exam day

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subjectYesSubject code
test_idYesTest ID (numeric string)
response_formatNomarkdown
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses that it returns only problem IDs (not content), explains test composition, limitations on availability, and time limits. No contradiction with annotations.

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?

Well-structured with clear sections and bullet points, but excessively verbose. Many sentences could be condensed without losing clarity.

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?

Given no output schema, the description explains the response format (array of IDs, order, count) and covers edge cases (invalid IDs, availability). All aspects needed for an agent to use the tool correctly are addressed.

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

Parameters5/5

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

Adds meaning beyond the schema by explaining the response_format parameter (output format), constraints on test_id (valid, numeric, availability), and the difference between test_id and category IDs. Schema coverage is 67%, and description compensates thoroughly.

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?

Clearly states the tool retrieves all problem identifiers for a specific test variant. Distinguishes from sibling tools, especially sdamgia_get_category_problems, by emphasizing curated test sets vs thematic collections.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use scenarios and a dedicated 'DISTINCTION FROM CATEGORY QUERIES' section explaining when not to use this tool, with clear alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/art22017/sdamgia-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server