Skip to main content
Glama

get_session

Read-only

One booked session by id (from list_sessions): time, type, location or meeting link, status and notes.

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": {
      "id": "<id>"
    },
    "name": "get_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered without the description. The description adds value by naming the returned fields, which matters because there is no output schema, but it does not say what happens with an unknown or deleted id (empty result vs error), leaving the main behavioral unknown unaddressed.

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?

One compact sentence, front-loaded with the identity of the resource and followed by the payload fields. Every clause earns its place and nothing is repeated from the schema or annotations.

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 tool with readOnlyHint annotations and no output schema, the definition covers purpose, id provenance, and return contents — sufficient to call it correctly. The only remaining gap is edge-case behavior for missing or unauthorized sessions, which is minor at this complexity.

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?

Schema coverage is 0% — the single id parameter has no description, so the description carries the burden. It specifies that the id identifies exactly one booked session and originates from list_sessions, adding genuine meaning beyond the bare string schema, though it does not state whether ids are opaque or whether a class-session id also works.

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 ("get one booked session by id") and enumerates the fields carried in the result (time, type, location or meeting link, status, notes), which tells an agent exactly what it will receive. Differentiation from siblings is indirect: it points at list_sessions as the id source but doesn't explicitly contrast with single-session mutation tools like cancel_session or mark_session_done.

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 parenthetical "(from list_sessions)" gives a concrete pointer on where the required id comes from, which is real usage guidance. There is no statement of when to prefer this over alternatives (e.g. after booking to confirm details) and no exclusions, so guidance remains implied rather than explicit.

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.