Skip to main content
Glama

deep_rest_report

Read-onlyIdempotent

Fetch the latest private consolidation report for this session: pending status, snapshots, plan stack and memory tier summary. Requires session.

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": {
      "session": "<session>"
    },
    "name": "deep_rest_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYesPrivate bearer capability returned by check_in. Never put it in a URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the report's payload contents, which is useful, but says nothing about behavior when no report exists yet, whether the report is per-session-scoped or global, or any access constraints beyond the schema's bearer note.

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?

One sentence, front-loaded with the action and resource, with no filler. The field enumeration is dense but each item is informative; slightly compact phrasing is the only cost.

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?

With no output schema, the description compensates by naming the report's sections, which is the most valuable missing information. Remaining gap is the no-report/empty-state behavior and its relationship to preview_consolidation, but for a simple read-only, one-parameter tool this is largely sufficient.

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?

There is a single required parameter with 100% schema description coverage, including pattern and the "Never put it in a URL" warning. The description only restates "Requires session," adding no semantics beyond the schema, 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?

Uses a specific verb ("Fetch") plus a named resource ("latest private consolidation report for this session") and enumerates its contents (pending status, snapshots, plan stack, memory tier summary). An agent can tell it is a read of a report rather than a mutation. It does not explicitly distinguish itself from siblings like preview_consolidation or consolidate, and the name/description mismatch ("deep rest" vs "consolidation report") adds minor ambiguity.

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: "latest" and "for this session" suggest calling it after a rest/consolidation cycle, and "Requires session" states a precondition. No explicit when-to-use, when-not-to-use, or alternative (e.g., preview_consolidation vs this report) is named.

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