Skip to main content
Glama

Между Комнат: двери в Москве

Разделы каталога

razdely
Read-onlyIdempotent

Разделы и подборки каталога me-ko.ru: межкомнатные, входные, скрытые двери, системы открывания, перегородки, погонаж, фурнитура, а также подборки по цвету, назначению и бренду. Поле razdel передайте в poisk.

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": "razdely"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered without description help. The description adds no behavioral detail beyond content enumeration — no note on the shape, size, or ordering of the returned section list. Adequate but not additive for a read-only listing tool.

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?

Front-loaded with the resource, then the category enumeration, then the single actionable instruction. Efficient, though the long comma-separated category list could be trimmed without losing selection signal.

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 zero-parameter discovery tool with no output schema, the description gives enough: what it returns (catalog sections/collections) and how to consume the result (feed razdel to poisk). Nothing essential is missing, though a hint at the returned structure would have been a bonus.

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 per the baseline this dimension starts at 4. The mention of the 'razdel' field applies to the sibling poisk rather than this tool, so it does not create confusion about this tool's own (empty) signature.

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 (catalog sections and collections of me-ko.ru) and enumerates the exact content categories — doors, opening systems, partitions, moldings, hardware, plus collections by color/purpose/brand — so an agent can tell it apart from siblings like poisk or tovar. The verb is implicit (it is a noun phrase), which keeps it from a 5, but the scope is unmistakable.

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?

It explicitly routes the agent forward: "Поле razdel передайте в poisk" tells the caller that this tool feeds the search flow. That is clear usage context, but there is no when-not-to-use statement or a comparison against the other siblings (tovar, raschet).

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