Skip to main content
Glama

Сделка с лентой

get_deal
Read-onlyIdempotent

Одна сделка: поля, человек и последние 30 событий ленты (заметки менеджеров, переводы, открытие доступа, оплаты). Помогает ответить, что с человеком происходит и о чём с ним договорились. Если у ключа нет области «имена» или школа не разрешила ИИ персональные данные, текст есть только у заведения сделки, переводов без причины, доступа и оплат без названия счёта, у остальных событий подпись вида.

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": {
      "deal_id": "<deal_id>"
    },
    "name": "get_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
deal_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, yet the description adds real operational context: the response is capped at the last 30 feed events, and text availability depends on the key's "имена" scope and the school's AI personal-data permission, with fallback signatures on redacted events. This is exactly the kind of permission- and truncation-behavior an agent cannot get from structured fields. It loses a point because the final clause is cut off ("подпись вида."), leaving the redaction format unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The payload is stated up front and the sentences are dense rather than padded. However, the trailing permission caveat is long, and its final clause is truncated mid-sentence, which adds ambiguity rather than information.

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 one-parameter read-only tool with no output schema, the description tells the agent what comes back (fields, person, 30 events) and how data may be masked. The remaining gaps are the unexplained deal_id source and the broken final clause.

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

Parameters2/5

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

Schema description coverage is 0% for the single deal_id property, so the description carries the full burden — yet it never mentions the parameter, its type, or where a valid id comes from (presumably list_deals). Only the noun "одна сделка" hints at identifying a deal by id.

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?

"Одна сделка: поля, человек и последние 30 событий ленты" names both the resource (single deal) and the exact payload it returns, and the following sentence adds the question it answers. The singular "одна" implicitly separates it from list_deals, but no sibling is named for contrast.

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?

"Помогает ответить, что с человеком происходит и о чём с ним договорились" gives the investigative use case, which implies when to reach for it. There is no explicit when-not or pointer to list_deals / add_deal_note as the follow-up or alternative, so the agent must infer routing.

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