Skip to main content
Glama

What a session wrote

session_prose
Read-onlyIdempotent

Retrieve the prose an agent wrote in a session, newest first, to recall earlier answers and explanations rather than tool output.

Instructions

The prose the agent wrote in a session (its answers and explanations, not tool output), newest first. Notes marked fragment read as mid-thought.

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_id": "<session_id>"
    },
    "name": "session_prose"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many passages (default 5, at most 20).
session_idYesThe session's id, from recent_sessions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations, which already establish read-only and idempotent behavior, the description discloses that results are newest first and that notes marked fragment should be read as mid-thought. It does not cover missing-session behavior, but the added context is valuable.

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?

The description is two tight sentences with the key scoping detail front-loaded and no wasted wording. The fragment-caveat is useful and compact.

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 adequately explains the returned content, ordering, and fragment caveat. It could do slightly more to describe edge cases such as a session with no prose, but it is complete enough for this simple read tool.

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 coverage is 100%, so both session_id and limit are already fully documented in the input schema. The description adds no parameter-level meaning beyond what the schema provides, which is the expected baseline.

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?

The description clearly identifies the resource: prose written by the agent in a session, explicitly excluding tool output. It does not explicitly distinguish this tool from sibling tools such as search_prose, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no explicit guidance on when to use this tool versus alternatives like search_prose or session_summary. The intended use is only implied by the resource description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.