Skip to main content
Glama

List goals

list_goals
Read-only

Metas da conta com o progresso calculado agora: feito, alvo, esperado até hoje (ritmo em dias úteis), quanto falta, quanto por dia útil e a situação (no_ritmo, abaixo, bem_abaixo, atingida, nao_comecou, encerrada, dentro_do_alvo, fora_do_alvo). Responde "estou no ritmo da meta?".

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

Input Schema

NameRequiredDescriptionDefault
idNoSó esta meta
arquivadasNotrue inclui as arquivadas

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive and closed-world behavior, so the bar is lower; the description still adds real value by disclosing that progress is calculated at call time, that pacing uses business days, and by enumerating the eight possible status outcomes. It omits any note on result volume or ordering.

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?

A single dense sentence front-loads the core purpose, then enumerates fields and statuses; every element carries information, though the eight-value status list makes it a long read and a short gloss on the statuses would have been tighter.

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 no output schema, the description does the necessary work of explaining the returned shape, including derived fields and status values, which is exactly what an agent needs to interpret results. Some ambiguity remains about default filtering when arquivadas is omitted and about language consistency with the English tool name.

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 description coverage is 100%, so both parameters are already documented and the description adds nothing about them. Its added meaning is on the return side (computed fields and status vocabulary), not on parameter semantics.

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 the resource (account goals) and specifies that progress is computed at request time, listing the exact derived fields returned. It does not distinguish itself from the sibling list_goal_metrics, so an agent must guess which of the two to use for metric-level data.

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?

The closing sentence names the question the tool answers ("am I on pace for the goal?"), which implies its use case. There is no explicit when-not guidance and no named alternative, and the interaction between the arquivadas flag and the default result set is only inferable from the schema.

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