Skip to main content
Glama
art22017

СДАМ ГИА MCP Server

by art22017

Get Problem Catalog

sdamgia_get_catalog
Read-onlyIdempotent

Retrieves the complete hierarchical catalog of topics, subtopics, and problem categories with unique IDs for a specified subject.

Instructions

Retrieves the complete hierarchical catalog structure for a specified subject, including all topics, subtopics, and problem categories with their unique identifiers.

PURPOSE: This is the primary discovery tool for exploring what problem content is available on the platform. It returns the full taxonomy of problem categories organized by topics, enabling you to navigate and find specific types of problems.

WHEN TO USE:

  • Always use this FIRST when exploring a new subject to understand its structure

  • Use when you need to find category IDs for other tools (required prerequisite for sdamgia_get_category_problems)

  • Use when you need to understand the organization and topics available for a subject

  • Use when building problem sets and need to browse available content

  • Essential for discovering what problem types exist before querying specific categories

KEY PARAMETERS:

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

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

RESPONSE FORMAT: Returns an array of catalog entries, where each entry contains:

  • name: Human-readable topic/category name

  • id: Unique category identifier (required for other tools)

  • children: Optional array of subcategories (nested hierarchy)

The response is hierarchical - categories may contain subcategories, and leaf nodes represent actual problem categories you can query.

IMPORTANT NOTES:

  • This tool ONLY returns category structure and IDs, NOT actual problems

  • Must be called before using sdamgia_get_category_problems to obtain valid category_id values

  • Category IDs are specific to each subject - the same ID may mean different things across subjects

  • The catalog structure can change over time as new content is added

  • Response size can be large for comprehensive subjects

EXAMPLE WORKFLOW:

  1. Call sdamgia_get_catalog(subject='ege') to get all EGE categories

  2. Parse response to find desired category (e.g., "Quadratic Equations" with id='12345')

  3. Use category_id='12345' with sdamgia_get_category_problems to get actual problems

TYPICAL USE CASES:

  • "Show me all available topics for EGE mathematics"

  • "What categories exist under 'Algebra' for OGE?"

  • "Find the category ID for trigonometry problems"

  • "Browse the complete problem catalog structure"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subjectYesSubject code
response_formatNomarkdown
Behavior4/5

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

Annotations already indicate read-only, non-destructive, and idempotent. The description adds details that the tool returns only structure, not problems, and that IDs are subject-specific and may change over time, which are useful beyond annotations.

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

Conciseness5/5

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

The description is well-structured with sections (PURPOSE, WHEN TO USE, KEY PARAMETERS, etc.), each sentence adds value, and it is front-loaded with the core purpose.

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, provides an example workflow, and lists use cases. It is complete for a tool with two parameters and moderate complexity.

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 50%, but the description explains both parameters: subject (required, with context about its role) and response_format (optional, with default). It adds meaning beyond the enum values in the schema.

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 explicitly states the tool retrieves the hierarchical catalog structure for a subject, with verb 'retrieves' and resource 'catalog structure'. It distinguishes from siblings by noting it is a prerequisite for sdamgia_get_category_problems.

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 description provides clear when-to-use scenarios, such as 'first when exploring a new subject' and 'when you need category IDs for other tools'. It lacks explicit when-not-to-use statements but effectively implies 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