Skip to main content
Glama

matricula

Read-onlyIdempotent

Analyze all pending curriculum subjects to classify them as eligible, blocked by prerequisites, or unlocked through prerequisite chains, helping students plan enrollment.

Instructions

Analisa a elegibilidade de todas as disciplinas pendentes do currículo separando em elegíveis, bloqueadas por pré-requisito e o fecho transitivo destravado no curso.

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

Input Schema

NameRequiredDescriptionDefault
atualizarNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description usefully adds what is actually computed (the three eligibility categories and transitive closure), but it does not explain the effect of 'atualizar' — presumably a cache/data refresh — which is the one behavior an agent could get wrong.

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?

A single dense sentence with no filler, and the core purpose is front-loaded before the output breakdown. Slightly heavy phrasing ('o fecho transitivo destravado no curso') but nothing is wasted.

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 the annotations carry the safety profile. What remains missing is the semantics of the only input parameter and any signal about cost or data freshness, leaving the definition adequate but not self-sufficient.

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?

There is one parameter ('atualizar', boolean, default false) with 0% schema description coverage, and the description never mentions it. The meaning of refreshing versus using cached data must be guessed entirely, so the description fails to compensate for the schema gap.

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 verb and resource ('analisa a elegibilidade de todas as disciplinas pendentes do currículo') and enumerates the three output buckets (eligible, prerequisite-blocked, transitive closure unlocked). This makes the computation distinguishable from generic siblings like progresso or pendencias, though it never names an alternative 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 only implied: an agent can infer this is for planning enrollment / deciding what to register next, but the description gives no explicit when-to-use, when-not-to-use, or pointer to a sibling such as progresso or grade. The single opaque 'atualizar' flag is not contextualized as a usage decision either.

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