Skip to main content
Glama

Get Exploratory Session

get_session
Read-only

Retrieve complete details for an exploratory test session, including mission, status, assignee, release, attachments, issues, and findings, using either an internal ID or a counter-style ID.

Instructions

Get the full details of one exploratory session: name, mission, status, assignee, linked release, attachments, linked issues, findings. sessionId accepts either the internal _id or a counter-style ID like "SES-12".

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": {
      "projectId": "<projectId>",
      "sessionId": "<sessionId>"
    },
    "name": "get_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesProject ID
sessionIdYesInternal _id or counter-style ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.2.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / projectId / description
      Previous value: -"Project ID (required)."New value: +"Project ID"
    • changedInput schema / properties / sessionId / description
      Previous value: -"Internal _id or counter-style ID (required)."New value: +"Internal _id or counter-style ID"
  2. Addedv1.0.10

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by enumerating the payload surface (name, mission, status, assignee, linked release, attachments, linked issues, findings), which tells the agent how heavy the response is, though it says nothing about behavior when the ID is not found.

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 sentences, front-loaded with the operation and scope, with no filler. The second sentence partially restates the sessionId schema description, but the example makes it earn most of its place.

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?

There is no output schema, so the description carries the burden of describing return content and does so by listing the returned fields. Combined with annotations covering safety and a fully documented two-parameter schema, the definition is close to complete for a simple read tool; only not-found/error behavior is missing.

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 parameters are already documented in the schema itself. The description's only addition is the concrete example format 'SES-12' for sessionId, which is a marginal gain over 'Internal _id or counter-style ID' already in the schema.

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 opens with a specific verb and resource ('Get the full details of one exploratory session') and enumerates exactly what is returned, so the agent knows this is a single-record fetch rather than a list. It does not explicitly name a sibling to distinguish itself from, which keeps it 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 Guidelines3/5

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

Usage is only implied: fetch this when you need the complete record for a single session. There is no explicit when-to-use/when-not-to-use guidance and no mention of alternatives such as update_session for mutation or list/search tools for discovery.

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