Skip to main content
Glama

biblioteca

Read-onlyIdempotent

Checks a student's library loan status and account regularity in Pergamum/SIGAA, with an option to refresh the data.

Instructions

Verifica a situação de empréstimos e regularidade do estudante junto ao sistema de bibliotecas (Pergamum/SIGAA).

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

Input Schema

NameRequiredDescriptionDefault
atualizarNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.9/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 adds useful context by naming the external backends (Pergamum/SIGAA), but it never explains the `atualizar` flag, which implies a cache refresh and is the one behavior an agent could get wrong on an otherwise read-only tool.

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 front-loaded sentence with no filler, and the resource and system names come first. It is well-sized for the amount of information it chooses to convey.

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 explained, and the annotations carry the safety story. For a tool this simple, the remaining gap is the undocumented `atualizar` switch, which leaves the definition adequate but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter `atualizar` has 0% schema description coverage and is not mentioned in the description at all. With coverage this low, the description is expected to compensate, and it provides nothing about what refreshing means or when to set the flag.

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 ("Verifica") and a concrete resource: loan status and the student's regularity in the library system. Naming Pergamum/SIGAA makes the scope unambiguous. It stops short of differentiating itself from siblings like pendencias or status, which an agent might plausibly confuse it with.

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 explicit when-to-use guidance, no conditions for use, and no mention of alternative tools. The agent must infer that this is the tool for library loans rather than general pending-issues checks. Nothing tells it when this tool is the wrong choice.

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