Skip to main content
Glama

Альфа-Клиник (Alfa-Clinic, Moscow)

get_price

Read-onlyIdempotent

Published price list in RUB. Optional query and department group ID; confirm current prices with the clinic.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum records, default 20.
queryNo
offsetNoPagination offset, default 0.
group_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower. The description still adds genuine context beyond them: the currency (RUB), the fact that this is a published rather than authoritative price source, and the caveat to confirm current prices with the clinic — a real data-freshness warning. It says nothing about result volume or pagination behavior, but limit/offset defaults are documented in the schema.

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?

Two short sentences with the resource and currency front-loaded and the caveat last, so nothing is buried. The middle clause listing the optional parameters is terse to the point of being slightly clipped, but no sentence is wasted.

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

Completeness3/5

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

For a four-parameter tool with no output schema and half its parameters undocumented, the description leaves real gaps: it never says what a price record contains (service name, price, department) or how query matches. It does convey currency and source reliability, which are the most important contextual facts, but the return shape remains unknown.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: query and group_id carry no schema descriptions. The description partially compensates by clarifying that group_id is a 'department group ID' and that both are optional, but it never explains what fields the free-text query matches, leaving the most ambiguous parameter underspecified.

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 states the resource and scope concretely: a published price list denominated in RUB. It is clear what data comes back, though the verb is only implied by the tool name and it draws no boundary against siblings such as get_service or list_services, which likely also expose pricing-adjacent data.

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 only implied: the agent learns this returns the published price list and that prices should be confirmed with the clinic. There is no statement of when to prefer this over siblings like get_service, nor any precondition or exclusion, so routing must be inferred from the name alone.

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