ufsc-moodle-mcp

Consultar nota e tentativas de um aluno em um questionário

get_quiz_grade

Read-onlyIdempotent

Retrieve a student's best quiz grade and attempt history from Moodle by quiz and student IDs to review performance.

Instructions

Retorna a melhor nota e o histórico de tentativas de um aluno em um questionário (quiz) do Moodle.

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": {
      "quizId": "<quizId>",
      "studentId": "<studentId>"
    },
    "name": "get_quiz_grade"
  }
}

Input Schema

Name	Required	Description	Default
`quizId`	Yes	ID do questionário (quizId).
`studentId`	Yes	ID do aluno (userid).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Nov 7, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that the response includes both the best grade and the attempt history, which beyond that it says nothing about ordering of attempts, whether all attempts are returned, or permission requirements.

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?

One front-loaded sentence with no filler; the parenthetical '(quiz)' is the only mild redundancy. It is efficient, though it offers no structure beyond the single statement.

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?

For a two-parameter read tool with no output schema, the description covers the essentials and briefly indicates the return content (best grade plus attempt history). It could say more about what the attempt history contains, but nothing critical to invoking the tool correctly 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 coverage is 100%, with both quizId and studentId documented in the schema (including the userid clarification). The description introduces no additional parameter semantics, so the baseline 3 applies.

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 names a specific verb ('Retorna') and specific resources ('melhor nota e o histórico de tentativas de um aluno em um questionário do Moodle'), so an agent can distinguish it from get_quizzes, which presumably lists quizzes rather than reporting one student's results. It does not name that sibling explicitly, so it falls short of full differentiation.

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?

The read-a-grade framing implies when to use it (when you have a quizId and studentId and need that student's score), but there is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as get_quizzes or the grading-batch tools. Usage is inferable but not routed.

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