Skip to main content
Glama
Plenera MCP

Plenera MCP

Official
by Plenera-io

get_session

Read-only

Read a visible agent session and recent activity, using before/after cursors to page through events.

Instructions

Read a visible agent session and recent activity. before/after are activity cursors.

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

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
beforeNo
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. Beyond that, the description adds 'visible' (unexplained permission scoping) and the cursor note, but says nothing about pagination direction, ordering, or what happens when cursors are invalid. For a tool with four undocumented parameters, the description carries too little behavioral context.

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?

Two short sentences, front-loaded with the core action and with no filler. However, the terseness crosses into under-specification rather than disciplined brevity—the second sentence is doing too little work for the schema gap it must cover.

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

Completeness2/5

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

With zero schema description coverage, no output schema, and four parameters, this description should do substantial heavylifting for parameter meaning and navigation behavior. It omits any explanation of 'session' and 'limit', and never clarifies the relationship to session_activity, leaving the definition materially incomplete for a paginated read tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, but it only labels before/after as 'activity cursors.' The required 'session' identifier and the 'limit' parameter (max 100) receive no explanation at all, so half the parameters remain opaque in both schema and description.

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

Purpose3/5

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

The description states a verb (read) and a resource (agent session), so the basic purpose is discernible. But it muddles the purpose by appending 'and recent activity,' which overlaps with the sibling session_activity without clarifying whether activity is included or how the two tools differ. An agent cannot confidently pick this over session_activity.

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?

No when-to-use guidance, no prerequisites, and no exclusions are given. The only implicit clue is the word 'visible,' which hints at access scoping but is never explained. The agent must infer eligibility from the sibling list alone.

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