Skip to main content
Glama

ver_estudos

Read-only

Lista as dúvidas de estudo ainda não resolvidas (com o número usado por resolver_duvida) e as aulas concluídas por módulo. Use para montar planos de revisão ou quando o usuário perguntar o que já estudou ou o que ficou pendente.

Instructions

Lista as dúvidas de estudo ainda não resolvidas (com o número usado por resolver_duvida) e as aulas concluídas por módulo. Use para montar planos de revisão ou quando o usuário perguntar o que já estudou ou o que ficou pendente.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.0
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "duvidas": {
      -      "description": "Dúvidas não resolvidas",
      -      "items": {
      -        "additionalProperties": false,
      -        "properties": {
      -          "criadaEm": {
      -            "type": "string"
      -          },
      -          "modulo": {
      -            "type": "string"
      -          },
      -          "numero": {
      -            "description": "Número usado por resolver_duvida",
      -            "type": "number"
      -          },
      -          "resolvida": {
      -            "type": "boolean"
      -          },
      -          "texto": {
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "numero",
      -          "modulo",
      -          "texto",
      -          "criadaEm",
      -          "resolvida"
      -        ],
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "progresso": {
      -      "additionalProperties": {
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "description": "Aulas concluídas por módulo",
      -      "propertyNames": {
      -        "type": "string"
      -      },
      -      "type": "object"
      -    }
      -  },
      -  "required": [
      -    "duvidas",
      -    "progresso"
      -  ],
      -  "type": "object"
      -}New value: +null
  2. Addedv1.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a safe read (readOnlyHint=true, openWorldHint=false), so the description need not re-argue safety. What it adds beyond them is meaningful: the returned doubt numbers are directly consumable by resolver_duvida, which is actionable context an agent would not get from the annotations alone. It does not describe ordering or how the module grouping is presented, leaving a minor gap.

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 with no filler. What is returned is front-loaded, and the usage context follows in the same breath, so the agent hits the essential information first.

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 zero-parameter, read-only list tool with no output schema, the description covers what comes back and why to call it, which is enough to invoke it correctly. Only minor presentation details, such as result ordering or grouping format, are left implicit.

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?

The tool takes no parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The description correctly implies the listing is unscoped, returning all pending doubts and completed lessons rather than a filtered subset.

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 names a specific verb ('Lista') and two concrete resources: unresolved study doubts and lessons completed per module. It also distinguishes what it returns from the sibling that consumes it, noting the doubt numbers are the ones used by resolver_duvida, so an agent can tell the two tools apart without opening a 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 explicit use cases: build review plans, or answer when the user asks what they have already studied or what is still pending. That is a clear usage context, but it does not state any exclusion or a contrasting alternative (e.g., when to prefer listar_modulos instead), so it stops short of full when/when-not guidance.

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