Skip to main content
Glama

preparar_lancamentos_mentoria

Read-onlyIdempotent

Computes what to log to today's study goals by matching incomplete mentorship goals to TecConcursos subjects and question/accuracy figures from your latest performance spreadsheet.

Instructions

Calcula o que lançar nas Metas Diárias da mentoria a partir da planilha de Desempenho mais recente.

metas: títulos das metas de hoje ainda não concluídas, como aparecem na página (ex.: ["Simulado de Informática", "Simulado de Direito Constitucional (VTM)"]). Não acessa a mentoria: só devolve, por meta, a matéria do TecConcursos casada e as questões/acertos. Mostre o resultado ao usuário e peça confirmação antes de preencher qualquer coisa.

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": {
      "metas": "<metas>"
    },
    "name": "preparar_lancamentos_mentoria"
  }
}

Input Schema

NameRequiredDescriptionDefault
metasYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, but the description adds real substance: it reads the most recent Desempenho sheet, does not touch the mentorship, and returns per-goal the matched TecConcursos subject plus question/accuracy figures. It stops short of saying what happens when a goal title matches no subject (error, omission, or partial result).

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?

It is short and front-loaded: the effect sentence comes first, the parameter explanation with example second, the capability caveat and the confirmation instruction last. The only slight redundancy is restating 'metas' after the opening clause, and the inline line breaks fragment the flow a little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only tool with an output schema, everything an agent needs is present: data source, non-mutating behavior, input format, returned shape, and the mandatory confirmation step before any filling. No output-schema explanation is required, and none is given.

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

Parameters5/5

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

Schema coverage is 0% — the schema only names the field 'Metas' — so the description carries the whole burden for the single required parameter. It defines the array contents as today's goal titles that are not yet completed, requires exact page wording, and supplies a concrete two-element example, which is far beyond a baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific verb and output: it computes what to launch into the mentorship's daily goals from the most recent Desempenho spreadsheet. The clause "Não acessa a mentoria: só devolve, por meta, a matéria do TecConcursos casada e as questões/acertos" draws a hard line between this calculation step and the sibling that actually writes to the mentorship.

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?

The description clearly frames the workflow: compute first, show the result, ask the user for confirmation, and only then fill anything in — which implicitly routes the write step to registrar_lancamentos_mentoria. It never names that sibling or states an explicit when-not condition, so the routing is strongly implied rather than spelled out.

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