Skip to main content
Glama

resolver_duvida

Idempotent

Marks a study doubt as resolved using the doubt number shown in your study list. Use it only when explicitly requested to close or clear a specific doubt.

Instructions

Marca uma dúvida como resolvida, pelo número mostrado em ver_estudos. Chame apenas quando o usuário pedir explicitamente.

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": {
      "numero": "<numero>"
    },
    "name": "resolver_duvida"
  }
}

Input Schema

NameRequiredDescriptionDefault
numeroYesNúmero da dúvida, como mostrado em ver_estudos (#3 → 3)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the mutation and idempotency profile is covered. The description's real addition is the confirmation requirement (only on explicit user request); it says nothing about reversibility or how a wrongly resolved question can be undone.

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 short sentences, front-loaded with the action and followed by the condition. No filler and nothing to trim.

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 single-parameter mutation with no output schema and reasonably rich annotations, the description covers what the tool does, where the parameter value comes from, and when it may be invoked. Only the result of calling it (what is returned or confirmed) is left unspecified, which is a minor gap.

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 schema description already documents the integer range and the '#3 → 3' mapping. The description's pointer to ver_estudos as the place the number comes from is helpful but largely duplicates 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.

Purpose5/5

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

The description states a specific verb and resource ('Marca uma dúvida como resolvida') and points to the sibling tool ver_estudos as the source of the parameter, so the agent can tell it apart from registrar_duvida without opening either schema.

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?

It gives a clear gating rule ('Chame apenas quando o usuário pedir explicitamente'), which is exactly the when-to-use constraint needed for a state-changing tool. It does not contrast with alternatives for reopening or editing questions, so it stops short of a full when/when-not comparison.

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