Skip to main content
Glama

registrar_lancamentos_mentoria

Records locally which mentorship entries were already saved, using the spreadsheet and saved items, to prevent duplicate logging in future runs.

Instructions

Anota localmente (mentoria_lancados.json) o que JÁ foi salvo na mentoria, para não lançar de novo.

planilha: o campo planilha devolvido por preparar_lancamentos_mentoria. lancamentos: itens efetivamente salvos, cada um com meta, materia_tec, questoes e acertos.

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": {
      "planilha": "<planilha>",
      "lancamentos": "<lancamentos>"
    },
    "name": "registrar_lancamentos_mentoria"
  }
}

Input Schema

NameRequiredDescriptionDefault
planilhaYes
lancamentosYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations only declare the generic write profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false); the description adds the useful fact that state is written to a local file, mentoria_lancados.json. It does not say whether repeated registrations append, overwrite or duplicate entries, which matters given idempotentHint=false and the stated dedup intent.

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?

Three short blocks: a front-loaded purpose sentence followed by one line per parameter, using backticked names for scannability. No redundant phrasing and nothing that merely restates the tool name.

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?

With an output schema present, return values need no explanation, and the description covers purpose, storage location and both inputs. It stops short of describing failure or duplicate-handling behavior for a stateful write, which is the one remaining gap for an agent calling it correctly.

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 has to carry the parameter meaning, and it does: `planilha` is identified as the field returned by `preparar_lancamentos_mentoria`, and `lancamentos` is defined as the items actually saved with the fields meta, materia_tec, questoes and acertos. Only format-level detail (types, whether `planilha` is a raw string or path) is left unstated.

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?

States a specific verb ("Anota localmente") and resource (what was already saved in the mentoria), plus the goal "para não lançar de novo". It also names the sibling that produces the `planilha` input, so the agent can place it in the workflow without opening the schema.

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 implied: call this after items are actually saved, to avoid re-launching them, and take `planilha` from `preparar_lancamentos_mentoria`. There is no explicit statement of when NOT to call it, nor what to do if a partial save failed, leaving ordering to inference.

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