Skip to main content
Glama
Sign In
magents

magents

by abnegate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

get_session

Look up a session by ID, live name, title, PID, or agent:ref. Retrieve session details to coordinate handoffs between coding agents.

Instructions

Look up one session by id, live name, title, pid, or agent:ref.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
session_idYesSession id, live name, title fragment, `agent:ref`, or `latest`

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral meaning itself. 'Look up' suggests a read-only operation, but the description gives no detail on not-found behavior, title-fragment matching, or whether the operation has any broader side effects or constraints.

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 sentence with no filler, front-loading the action and resource before the identifier variants. Every word contributes to the purpose.

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?

The description is adequate for a simple single-session lookup, and the schema fills in the 'latest' option. The optional limit semantics and the multiple-match risk of a 'title fragment' are not clarified, so it is minimally complete rather than comprehensive.

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?

The description adds value by exposing identifier aliases, including 'pid', beyond the schema's session_id text. It does not explain the limit parameter, which is also undocumented in the schema, so semantic coverage is only partial.

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?

The description states a specific action ('look up') and a specific resource ('one session'), then enumerates accepted identifier forms: id, live name, title, pid, and agent:ref. The singular 'one' clearly contrasts with the sibling list_sessions, making the purpose unambiguous.

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?

It implies the tool should be used when a single session is needed by a known identifier. However, it does not explicitly say when not to use it or name alternatives such as list_sessions or session_digest, so the agent must infer the boundary.

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

Deploy Server

Other Tools