KiroStats
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_sessionA | Start tracking a new chat session. Call this ONCE at the beginning of every chat session. Captures a snapshot of current plan credits and wall-clock time so that subsequent calls to get_session_stats can calculate deltas. Returns the session_id and starting credit balance. |
| log_interactionA | Log an agent interaction (turn) within the session. Call this after each agent turn to record thinking time. If thinking_seconds is not provided, records a zero-duration ping (useful for just updating the 'last activity' timestamp). |
| get_session_statsA | Get current metrics for a chat session. Returns:
|
| get_plan_usageA | Get overall Kiro plan usage for the current billing cycle. Returns plan limit, total credits used, remaining, overage details, and reset date. This is the full-cycle view (not session-specific). |
| get_session_summaryB | Get a formatted summary suitable for pasting into Jira comments, PR descriptions, or other documentation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
All tools have distinct purposes: plan-level usage, session metrics, session summary, interaction logging, and session initiation. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case (get_plan_usage, get_session_stats, get_session_summary, log_interaction, start_session). No deviations.
5 tools is well-scoped for a session and usage tracking server. Each tool serves a clear need without redundancy or gaps.
Covers the full lifecycle: session start, per-turn logging, current stats, formatted summary, and plan-level usage. No obvious missing operations for the intended domain.