Skip to main content
Glama
art22017

СДАМ ГИА MCP Server

by art22017

Get СДАМ ГИА Problem by ID

sdamgia_get_problem
Read-onlyIdempotent

Retrieve a complete exam problem from the СДАМ ГИА database by its unique ID. Includes problem statement, solution, answer, and similar problems.

Instructions

Retrieves a complete problem from the СДАМ ГИА database by its unique identifier.

When to use:

  • You have a specific problem ID and need its full details

  • You need to see the problem statement, solution, answer, and similar problems

  • You want to reference an exact problem from the СДАМ ГИА database

Parameters:

  • subject (required): Subject code (e.g., 'math', 'phys', 'inf', 'rus', 'chem', 'bio', 'geo', 'hist', 'soc', 'en', 'de', 'fr', 'sp', 'lit')

  • problem_id (required): Numeric problem ID as a string (e.g., "12345")

  • response_format (optional): Output format - 'markdown' (default, human-readable) or 'json' (structured data)

Returns: A complete problem object containing:

  • condition: The problem statement (text and optional HTML/images)

  • solution: Step-by-step solution with explanations

  • answer: The correct answer

  • similar_problems: List of related problem IDs for further practice

  • metadata: Problem ID, subject, difficulty level where available

Response format:

  • Markdown: Formatted text with sections for condition, solution, answer, and similar problems

  • JSON: Structured object with all problem data as nested objects/arrays

Example: Getting a specific math problem:

{
  "subject": "math",
  "problem_id": "54321",
  "response_format": "markdown"
}

Notes:

  • Problem IDs must be numeric strings (digits only)

  • The problem_id must exist in the specified subject database

  • Some problems may not have solutions available

  • Similar problems are automatically included for practice

  • Use this tool when you need exact problem details, not for searching

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subjectYesSubject code (e.g., 'math', 'phys', 'inf')
problem_idYesProblem ID (numeric string)
response_formatNoOutput format: 'markdown' for readable text or 'json' for structured datamarkdown
Behavior5/5

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

Adds constraints (numeric ID, existence prerequisite), content expectations (possible missing solutions), and behavior (similar problems included), going well beyond the 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?

Well-structured with clear headings and front-loaded purpose; every sentence adds value without redundancy.

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?

Compensates for missing output schema by detailing return object structure, and covers edge cases and metadata; sibling differentiation is clear.

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?

Schema coverage is 100%, but description adds examples, enum context, default explanation, and input example, enhancing understanding.

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 it retrieves a complete problem by unique identifier, distinguishing it from sibling tools like batch retrieval or search.

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 an explicit exclusion ('not for searching'), with alternatives implied by sibling names.

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