Skip to main content
Glama

configurar

Idempotent

Stores a UFC student's numeric course ID and university restaurant name so SIGAA calendar and restaurant menu queries can be personalized. Prompt for both values first.

Instructions

Primeiro uso: grava o id numérico do seu curso (o mesmo do calendário público do SIGAA) e o nome do restaurante universitário (ex.: Fortaleza, Pici, Quixadá, Sobral). Pergunte esses dados ao estudante antes de chamar; não invente valores.

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

Input Schema

NameRequiredDescriptionDefault
cursoNo
restauranteNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare write (readOnlyHint=false), idempotent, and non-destructive, so the safety profile is covered. The description adds that values are persisted and where the course id comes from (the SIGAA public calendar), which is genuine context. It doesn't say whether a second call overwrites existing config or how validation failures behave.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the "primeiro uso" qualifier, then the data needed, then the precondition on the caller. No redundant restatement of the tool name or schema.

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 configuration tool with an output schema and clear annotations, the description covers what to supply, where it comes from, and the caller's obligation to ask the user. The only gap is behavior on repeat invocation, which 'primeiro uso' implies but doesn't settle despite the idempotent hint.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry both parameters — and it does: curso is a numeric id matching the SIGAA public calendar, restaurante is the restaurant name with concrete examples (Fortaleza, Pici, Quixadá, Sobral). Neither parameter is left ambiguous, though the exact id format/range is still implicit.

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?

"Grava o id numérico do seu curso ... e o nome do restaurante universitário" names a specific verb (save) and both resources it persists, so an agent knows exactly what the tool does. It doesn't explicitly contrast with siblings like restaurantes or calendario_curso, but the "primeiro uso" framing makes its role clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Primeiro uso" gives an explicit trigger condition, and "Pergunte esses dados ao estudante antes de chamar; não invente valores" states a hard prerequisite and a prohibition on fabricated input. What's missing is routing to alternatives (which sibling to call first to discover the course id or restaurant list) and what to do if already configured.

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