Skip to main content
Glama

Extreme Drive — extreme driving school

Карточка программы

get_program
Read-only

Одна программа по числовому id из list_programs: цена и состав курсов. Если программы нет на витрине сайта, вернётся ошибка.

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": {
      "program_id": "<program_id>"
    },
    "name": "get_program"
  }
}

Input Schema

NameRequiredDescriptionDefault
program_idYesID программы (iblock 110)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value beyond that: what comes back (price and course composition) and a concrete failure mode — an error is returned when the program is not present on the site showcase, i.e. the read scope is limited to published items.

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?

Two short sentences, zero filler. The core identity of the tool is front-loaded, followed by the return payload and the error condition, in the order an agent needs them.

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

Completeness4/5

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

For a single-parameter read tool with no output schema, the definition covers the essentials: identity, id provenance, returned fields, and the error case. Only the exact shape of the returned price/course-composition object is left unspecified, which is a minor gap given there is no output schema to lean on.

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% and the parameter already documents itself as an iblock 110 id, so the schema carries the baseline. The description still adds meaning by stating the id is numeric and must be sourced from list_programs, which tells the agent how to obtain a valid value rather than guessing.

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 in the very first words — fetch a single program by numeric id — and explicitly contrasts it with list_programs, so an agent can distinguish the single-item getter from the sibling list tool without opening either schema. It also names the payload (price and course composition), which sharpens the purpose further.

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

Usage Guidelines3/5

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

The phrase 'по числовому id из list_programs' tells the agent where the required id comes from, which is genuine routing guidance. However, it gives no explicit when-not-to-use guidance relative to get_course or get_guide, and no prerequisites beyond the id provenance, so usage is implied rather than spelled out.

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