Skip to main content
Glama

score_sessions

Scores recent agent sessions on prompt clarity, context efficiency, rework, consistency, and completion, then lists lowest and highest performers; optionally writes a Markdown report.

Instructions

Score recent sessions on prompt clarity, context efficiency, rework, consistency and completion, and list the lowest and highest scorers. If report_path is given, also writes the report as local Markdown.

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

Input Schema

NameRequiredDescriptionDefault
projectNo
sourcesNoall
days_backNo
report_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose one genuine side effect: it writes a Markdown report to disk when report_path is supplied. It also names the scoring dimensions, which is useful behavioral context. It says nothing about scope limits (how many sessions are considered 'recent'), cost, or what happens when project/sources are omitted.

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 scoring action and its dimensions, followed by the optional report write. No filler, though the dimension list is a bare enumeration without any hint of how they combine.

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?

An output schema exists, so return values need not be explained, which relieves some burden. But for a four-parameter, zero-coverage, unannotated tool with a filesystem side effect, the description leaves too much unstated about filtering scope and output destination semantics to be considered complete.

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

Parameters2/5

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

Schema description coverage is 0% for four parameters, so the description must compensate and it largely does not. It explains report_path's effect and hints at recency via 'recent sessions' (days_back), but project and sources — including the meaning of the 'all' default — are entirely unaddressed in both schema and description.

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?

States a specific verb and resource (score sessions) and enumerates the five scoring dimensions, plus the output shape (lowest and highest scorers). It does not, however, distinguish itself from close siblings such as analyze_sessions, get_session_scorecard, or compare_sessions, so an agent must infer the boundary.

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?

There is no explicit when-to-use guidance, no statement of when another tool is preferable, and no prerequisites. Only the conditional behavior of report_path is described, which is about how the tool runs, not when to pick it.

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