Skip to main content
Glama

Student Results

student_results
Read-only

Retrieves a student's course results for monitoring and analysis; provide a student ID to view performance across enrolled courses.

Instructions

Resultados de un alumno en sus cursos (monitor).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "student_id": "<student_id>"
    },
    "name": "student_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
student_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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 tells the agent this is a safe read, so the description needs to add context such as whether "monitor" implies a role requirement, tag-based scoping, or partial results. It adds none of that, leaving the ambiguity unresolved.

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?

One short sentence with no wasted clauses, so it is concise, but it is under-specified rather than efficient. The parenthetical "(monitor)" is appended without explanation and carries no clear meaning.

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 described, and this is a single-parameter read tool. Still, the undefined "(monitor)" term and the lack of differentiation from similar result tools leave the definition only minimally 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% and the single parameter student_id has only a type. The phrase "de un alumno" weakly implies the parameter identifies a student, but there is no statement of format, source, or what happens for an unknown id.

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?

"Resultados de un alumno en sus cursos" names a resource (results) and a scope (one student, across courses), which is more than a tautology. However it never distinguishes itself from siblings like course_results or test_results, and the trailing "(monitor)" is cryptic rather than clarifying.

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 when-to-use guidance at all: the description does not say when to pick this over course_results or test_results, nor when it is inappropriate. The only contextual hint is the ambiguous "(monitor)" tag, which an agent cannot reliably act on.

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