Skip to main content
Glama
Sign In
daimonos

daimonos

by beardfaceguy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

session_stats

Get token usage statistics for current session, historical cross-session data, and daily trends. Filter by external session ID for single agent-runtime session analysis.

Instructions

Token analytics. Scopes: session (current totals), history (cross-session), daily (trend). Optional external_session_id filters history/daily to a single agent-runtime session id.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

Description mentions an optional parameter 'external_session_id' that does not exist in the schema (which has no parameters). This is a contradiction between description and schema. No information about side effects, permissions, or data returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief but contains inaccurate information (referencing a non-existent parameter). Conciseness is undermined by the lack of accuracy.

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?

Without output schema or annotations, the description should clearly explain return values. It does not describe what the tool outputs (e.g., format, fields). The scoping hints provide some context but not enough for complete understanding.

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

Parameters1/5

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

The input schema has zero parameters, but the description claims an optional 'external_session_id' parameter. This misleading addition degrades the agent's ability to invoke the tool correctly. Schema coverage is 100% for an empty schema, but the description adds false semantics.

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?

Description states 'Token analytics' with three scopes (session, history, daily), suggesting it returns token usage statistics. However, it does not specify what metrics are returned (e.g., count, cost, etc.), making the purpose only moderately clear.

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 guidance on when to use this tool over siblings like set_external_session_id. No preconditions or exclusions are mentioned, leaving the agent to infer usage context.

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