Skip to main content
Glama
Sign In
fiuba-mcp

fiuba-mcp

by agustinbn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fiuba_grades

Read-only

Retrieve a student's grade report for a Moodle course, including each graded item's grade, range, percentage, and feedback by course ID.

Instructions

The student's grade report for a course: each graded item with grade, range, percentage and feedback.

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": {
      "courseid": "<courseid>"
    },
    "name": "fiuba_grades"
  }
}

Input Schema

NameRequiredDescriptionDefault
courseidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/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 bar is lower. The description adds useful return-shape context (grade, range, percentage, feedback), which matters because there is no output schema, but it says nothing about authorization scope or behavior when no grades exist.

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 compact sentence with no filler, and the key noun (grade report for a course) is front-loaded. It is slightly under-specified rather than verbose.

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?

With no output schema, the description carries some of the return-value burden and does list the returned fields. However, it never clarifies that this is the authenticated student's own report, nor how filtering by course works, leaving the agent to infer call semantics.

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 the single courseid parameter, so the description must compensate. "for a course" loosely implies the parameter's meaning, but it omits the expected format (integer id) and where that id comes from (e.g., fiuba_list_courses).

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 is a noun phrase that identifies the resource (a course grade report) but never states a verb like "get" or "retrieve". It does not differentiate itself from siblings such as fiuba_get_course or fiuba_assignments, which plausibly return overlapping course data.

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 indication of when to use this tool versus fiuba_get_course or fiuba_assignments, and no mention of prerequisites such as the student needing to be enrolled. The intended context is only implied by the noun "grade report".

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

Deploy Server

Other Tools