Skip to main content
Glama

Журнал записей на встречи

get_booking_journal
Read-onlyIdempotent

Возвращает записи за период: кто записался, на какое время, в каком статусе, кто и почему отменил. В журнале персональные данные респондентов, поэтому он требует того же права, что и остальные результаты.

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": {
      "workspace_id": "<workspace_id>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "get_booking_journal"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesКонец периода, позже начала. Время без указания пояса считается UTC.
fromYesНачало периода. Дата или дата со временем; время без указания пояса считается UTC.
workspace_idYesID воркспейса (из workspace://list).

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: the journal contains respondents' personal data and requires the same permission as other results, which is a real access precondition an agent should know before calling.

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 sentences, no filler, and the most decision-relevant content (what is returned) is front-loaded before the access caveat. Every clause carries 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 three-parameter read tool with no output schema, the description compensates by enumerating the returned fields and stating the permission requirement. Only the lack of explicit sibling routing keeps it from being fully complete.

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 description coverage is 100%, with each of the three parameters documented in the schema including timezone handling for from/to. The description adds no syntax or semantic detail beyond what the schema already supplies, so the baseline 3 applies.

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?

States a specific verb and resource ('Возвращает записи за период') and enumerates the returned fields (who booked, time, status, who cancelled and why), so the agent knows exactly what data comes back. It does not explicitly contrast with sibling tools such as get_quiz_answers or the booking_block mutators, so it falls short of a 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?

The period-based scope implies when the tool applies, but there is no explicit when-to-use guidance, no exclusions, and no named alternative for related needs. The reader must infer usage from the description and sibling names.

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