Skip to main content
Glama

Item statistics

item_statistics
Read-onlyIdempotent

Retrieve each recorded item measurement—difficulty, discrimination, and dataset metrics—newest first with dataset, cohort, and commit context for one module or all items, without averaging.

Instructions

Every measurement recorded about each item (difficulty, discrimination, any metric a dataset supplied), newest administration first, with the dataset and cohort it came from; for one module's items or all. Nothing is averaged or summarized: each value is as recorded, with the commit it was measured against.

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

Input Schema

NameRequiredDescriptionDefault
refNoA commit id to read at, as an earlier answer named it: pass the commit from your first answer to every follow-up, so the conversation reads one state of the design. Pass this or branch, not both.
unitNoKeep only metrics in this unit; the answer lists the units present.
branchNoThe branch to read at its latest commit. Leave out to read the default branch (main unless configured otherwise). Pass this or ref, not both.
moduleNoA module's id, for its items only; every item when left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real context: ordering by newest administration, provenance (dataset, cohort, commit measured against), and the guarantee that values are unmodified rather than aggregated. This is exactly the kind of behavioral detail annotations cannot carry.

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?

Content is front-loaded into one dense sentence describing what is returned, ordering, and provenance, followed by a short clarifying sentence on non-aggregation. The semicolon chains are slightly heavy but every clause carries distinct information.

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?

With no output schema, the description carries the return-shape burden, and it largely does: it names the metrics, ordering, provenance fields, and scoping. Minor gaps remain, such as pagination behavior or whether items with no measurements appear, but nothing essential for a correct call 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 description coverage is 100%, so the schema already fully documents ref, branch, unit, and module, including the mutual exclusivity of ref and branch. The description's 'for one module's items or all' and 'with the commit it was measured against' echo the module and ref parameters without adding new format or constraint detail, so the baseline 3 is appropriate.

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 states a specific resource, 'every measurement recorded about each item', enumerates representative metrics (difficulty, discrimination), and scopes it to one module's items or all. It also draws a clear contrast with aggregation tools by saying nothing is averaged, so an agent can tell it apart from summary-style siblings without naming one explicitly.

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 implied rather than stated: the 'Nothing is averaged or summarized' clause hints this is the tool for raw per-item values, but there is no explicit when-to-use/when-not or named alternative. An agent must infer the choice from the metric examples and the module scoping.

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