Skip to main content
Glama
art22017

СДАМ ГИА MCP Server

by art22017

Get Category Problems

sdamgia_get_category_problems
Read-onlyIdempotent

Retrieve all problem IDs for a specific subject category to identify available problems before fetching their details or solutions.

Instructions

Retrieves all problem identifiers belonging to a specific problem category within a subject.

PURPOSE: Fetches the complete list of unique problem IDs for problems classified under a specific category. This enables you to identify exactly which problems exist in a category before retrieving their full details or solutions.

WHEN TO USE:

  • Use AFTER obtaining a category_id from sdamgia_get_catalog (required prerequisite)

  • Use when you need to see all available problems in a specific category

  • Use when building problem sets from particular topics

  • Use when you need to count how many problems exist in a category

  • Use when selecting specific problems before fetching their full content

  • Essential for batch operations on category-level problem sets

KEY PARAMETERS:

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

  • category_id (required): Unique category identifier obtained from sdamgia_get_catalog

  • limit (optional): Maximum number of problem IDs to return (for pagination or sampling)

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

PARAMETER CONSTRAINTS:

  • category_id MUST be a valid ID from the catalog - invalid IDs will return errors

  • If category has no problems, returns empty array

  • limit parameter truncates results if specified; otherwise returns all problems

  • Category IDs are subject-specific - same ID may exist in multiple subjects but refer to different content

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

  • Each ID represents a unique problem that can be fetched with other tools

  • IDs are typically numeric but returned as strings

  • Order of IDs may not be sequential or sorted

  • Array may be empty for new or unused categories

  • Total count of problems is included in response metadata

IMPORTANT NOTES:

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

  • You MUST call sdamgia_get_catalog first to obtain valid category_id values

  • category_id values are case-sensitive and must match exactly from catalog

  • Large categories may return hundreds or thousands of IDs

  • The same problem ID may appear in multiple categories (cross-categorized content)

  • Invalid or expired category IDs will cause the request to fail

EXAMPLE WORKFLOW:

  1. Call sdamgia_get_catalog(subject='ege') to browse categories

  2. Find desired category (e.g., id='12345' for "Derivatives")

  3. Call sdamgia_get_category_problems(subject='ege', category_id='12345')

  4. Receive array: [1001, 1002, 1005, 1102, ...]

  5. Use individual problem IDs with sdamgia_get_problem to get full content

TYPICAL USE CASES:

  • "Get all problems in the 'Quadratic Equations' category for EGE"

  • "List first 50 problems from category ID 54321"

  • "How many practice problems exist for this topic?"

  • "Collect all problem IDs for a specific category to analyze difficulty distribution"

  • "Build a randomized problem set from category 67890"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subjectYesSubject code
category_idYesCategory ID
limitNoMaximum number of results to return
response_formatNomarkdown
Behavior5/5

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

Annotations already show readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds significant behavioral context: returns only IDs, not content; valid category required; large categories; cross-categorization; empty array for unused categories; response format metadata.

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?

Well-structured with sections like PURPOSE, WHEN TO USE, KEY PARAMETERS, etc. Front-loaded with purpose. However, it is verbose and repeats some information (e.g., 'only returns IDs' mentioned multiple times). Could be more concise but still clear.

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 fully explains response format (array of IDs with metadata). Covers prerequisites, error conditions, example workflow, and use cases. All necessary information for an agent to use the tool correctly.

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 descriptions are minimal (subject, category_id, limit, response_format). Description adds detailed constraints, usage notes, and examples for each parameter. However, there is a contradiction: description says response_format default is 'json' while schema says 'markdown'. Also, description says limit returns all if unspecified, but schema default is 20. These inconsistencies reduce score.

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 clearly states it retrieves problem identifiers for a category within a subject. It distinguishes from siblings by noting it only returns IDs, not content, and that prerequisite catalog call is needed.

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 conditions, prerequisites (call sdamgia_get_catalog first), and indicates it is for ID retrieval before full content fetch. Implicitly tells when not to use by stating it returns only IDs.

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