Skip to main content
Glama

Konfirmu

konfirmu_ata_construir

Constrói uma ATA verificável a partir de uma reunião em JSON (motor Modo Reunião v2): facto só com toque da pessoa, «?» para campo sem dados, hash SHA-256. Não grava áudio nem transcreve.

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": {
      "reuniao": "<reuniao>"
    },
    "name": "konfirmu_ata_construir"
  }
}

Input Schema

NameRequiredDescriptionDefault
reuniaoYesReunião: {tipo, lingua?, agora?, segmentos:[{texto}], toques:[índices], promessas?, naoFicouClaro?}. Formato em tools/ata/README.md.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: facts are recorded only where a person gave a 'toque', missing fields render as '?', and a SHA-256 hash makes the artifact verifiable. It also rules out audio capture and transcription. It leaves open whether anything is persisted or how the result is returned, which keeps it from a 5.

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?

One dense sentence with the verb and artifact front-loaded, followed by the operative rules and the explicit exclusion. Nothing is wasted, though the compression into a single clause chain slightly hurts scannability of the behavior rules.

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?

For a one-parameter, nested-input tool with no annotations and no output schema, the description covers the conceptual output (verifiable ATA with hash and '?' placeholders) but never says what the call actually returns or where the ATA is stored. The agent knows what the tool guarantees but not what it hands back.

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

Parameters3/5

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

Schema coverage is 100% and the single nested parameter is documented in detail, including the segment/toque structure and a pointer to tools/ata/README.md. The description reinforces that the input is a meeting in JSON but adds no field-level meaning beyond the schema, so the baseline of 3 applies.

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 artifact: build a verifiable ATA (minutes) from a meeting supplied as JSON, naming the engine variant (Modo Reunião v2). That is far more than a restatement of the name. It does not explicitly contrast with the sibling tools, so it stops short of a 5.

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: the input must be a JSON meeting, and the closing note 'Não grava áudio nem transcreve' tells the agent this tool is not for audio or transcription. There is no explicit when-to-use framing or named alternative for cases where the agent lacks a structured meeting object.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources