Skip to main content
Glama

mark_session_done

Mark one of the coach's own sessions as done/completed (confirm-gated). Counts toward the client's used sessions; also corrects a session wrongly left as a no-show. Safe to repeat; refused for cancelled sessions. Get the session id from list_sessions.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "mark_session_done"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: the confirm gate means a preview is returned before execution, the mark counts toward the client's used sessions, repeat calls are safe, and cancelled sessions are rejected. Only the shape of the preview response and any permission requirements are left unstated.

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?

Three compact sentences, front-loaded with the action and gated nature, followed by side effects, idempotency, exclusion, and the id source. No sentence is filler.

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?

A mutating, confirmation-gated tool with no output schema, yet the description covers side effects, repeatability, refusal conditions, and id sourcing. It would be fully complete if it hinted at what the preview response contains or any role restriction.

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 50%, with confirm already documented in the schema as the execute-vs-preview switch; the description reinforces that as 'confirm-gated'. For the undocumented sessionId it supplies the source (list_sessions), which is the most useful thing an agent can be told about it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('mark ... session as done/completed') and scopes it to 'one of the coach's own sessions'. The added clause about correcting a session wrongly left as a no-show separates it from the sibling mark_session_no_show without needing to open either schema.

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?

Gives a concrete precondition ('Get the session id from list_sessions') and an explicit exclusion ('refused for cancelled sessions'), plus a corrective use case. It stops short of naming mark_session_no_show as the alternative for the opposite direction, so routing logic is implied rather than spelled out.

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.