Skip to main content
Glama

privacy_session_snapshot

Reads the current page of a privacy session as bounded text, without references or storage, so agents can inspect session content while respecting consent boundaries.

Instructions

Read the current page of a privacy session (bounded text, no refs, not stored).

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": "privacy_session_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose useful non-obvious traits: output is bounded/truncated, contains no element refs, and is not stored. It does not say whether the call errors on an unknown or ended session, whether it has side effects, or how much text the bound permits, which for a mutation-free read is an acceptable but incomplete disclosure.

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 short sentence plus a dense parenthetical; every clause earns its place and the key constraint (current page) comes first. No filler or restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read with no annotations and no output schema, the definition covers the shape of the return value reasonably well but leaves the required precondition (an active session), the ID's origin, and any paging semantics unexplained. The phrase "current page" hints at iteration without any parameter to advance it, which an agent cannot resolve from the definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter session_id, and the description never mentions it, so there is nothing telling the agent where the ID comes from (presumably privacy_session_start/open) or what form it takes. The description adds no meaning beyond the schema at the one point where it is needed.

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: "Read the current page of a privacy session." The parenthetical further narrows what comes back, so the agent knows this is a snapshot read rather than a stream or mutation. It does not name or contrast with siblings such as privacy_session_start or privacy_session_end, so it stops short of full differentiation.

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 when-to-use guidance: nothing says a privacy session must already be open, whether this can be called before privacy_session_start, or what to do instead when the caller wants events, logs, or a different view. The word "current" implies repeated polling but that is left to inference.

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