Skip to main content
Glama

List Attempts

list_attempts
Read-only

Retrieves test attempts with optional filters for test, course, student, date range, and score range, enabling targeted result analysis.

Instructions

Intentos de tests con filtros opcionales.

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

Input Schema

NameRequiredDescriptionDefault
test_idNo
end_dateNofecha ISO 8601 con zona.
course_idNo
max_scoreNo
min_scoreNo
start_dateNofecha ISO 8601 con zona (p. ej. 2026-03-01T00:00:00Z).
student_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

readOnlyHint=true already establishes this is a safe read, so the lower bar applies, yet the description adds nothing beyond that: no pagination, ordering, or volume expectations for a listing endpoint. It does not contradict the annotation, but it contributes almost no behavioral context.

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

Conciseness3/5

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

A single sentence with zero filler, but its brevity comes from omission rather than tight writing; there is no front-loaded verb, scope, or result-shape statement to anchor the reader.

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?

An output schema exists so return values need not be described, but for a seven-parameter filtered listing tool the definition is far too thin: filter semantics and behavior are missing, and an agent must reverse-engineer intent from parameter names alone.

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?

Seven parameters with only 29% schema coverage, and the description only gestures at 'filters' generically. It never clarifies that test_id, course_id, student_id, min_score, and max_score are combinable filters, nor whether score bounds are inclusive, leaving the majority of parameters undocumented anywhere.

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?

The description identifies the resource (test attempts) and that filtering is supported, which separates it from siblings like list_tests or course_results. But it is a bare noun phrase with no verb, so whether it lists, counts, or streams attempts is left implicit.

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?

'con filtros opcionales' implies callers may narrow results, but there is no when-to-use guidance, no mention of when to prefer this over student_results or course_results, and no note that no filters are required to get everything.

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