Skip to main content
Glama
Sign In
KiroStats

KiroStats

by BrennanWebb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_session_summary

Retrieve a formatted summary of a Kiro IDE session for pasting into Jira comments or PR descriptions.

Instructions

Get a formatted summary suitable for pasting into Jira comments, PR descriptions, or other documentation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_session_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idNoWhich session to summarize. Uses active session if not provided.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided; description only states it returns a summary. Fails to disclose any side effects, auth requirements, or error behavior for missing sessions, which is needed for a tool with no annotation coverage.

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?

Single, front-loaded sentence clearly stating purpose with no redundant information. Every word earns its place.

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?

Given the simple tool (one param, output schema exists), description is adequate but could briefly mention the output format or content to provide fuller context.

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 already fully describes the parameter (session_id) with default behavior. Description adds no extra meaning beyond what the schema provides, resulting in baseline score.

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?

Description clearly states the tool gets a formatted summary for documentation purposes. It uses specific verbs and resources but does not explicitly differentiate from siblings like get_session_stats.

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?

Implied usage for copying summaries into Jira/PRs, but no explicit when-to-use or when-not-to-use guidance, nor mention of alternatives among siblings.

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