Skip to main content
Glama

Extreme Drive — extreme driving school

Список курсов

list_courses
Read-only

Курсы, онлайн-курсы и универсальные сертификаты, которые сейчас показаны на сайте (/price/, /price/certificates.php, /online/, /moto/): названия, цены, доступна ли аренда учебной машины. Скрытые и архивные позиции не включаются. Без мерча.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_courses"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: only currently displayed items are returned, hidden and archived positions are filtered out, and merch is excluded. It does not discuss ordering or pagination, which is the only notable gap.

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?

A single front-loaded sentence with the resource first, then the site sections in a parenthetical, then two short exclusion clauses. Every clause carries information; the bare URL list is slightly opaque without explanatory framing, but it is compact rather than wasteful.

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?

There is no output schema, and the description compensates by naming the returned fields (names, prices, training-car rental availability) as well as the filtering rules. For a zero-parameter read-only listing tool, that covers what an agent needs before calling it; result ordering and volume limits remain unspecified but are minor.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly does not waste words on input semantics and instead spends its budget on scope.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely and enumerates the exact scope: courses, online courses, and universal certificates, tied to concrete site sections (/price/, /price/certificates.php, /online/, /moto/). It implicitly separates itself from list_programs by never mentioning programs, and the explicit "Без мерча" exclusion sharpens the boundary further. It stops short of naming a sibling to contrast against, which keeps it at 4 rather than 5.

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?

Usage is implied by "которые сейчас показаны на сайте" and by the exclusion of hidden and archived items, so an agent can infer this is the catalog-visibility listing. However, there is no explicit guidance on when to pick this over list_programs, get_course, or get_program, so the routing decision is left to inference.

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