Skip to main content
Glama

List goal metrics

list_goal_metrics
Read-only

Lista as métricas que uma meta pode usar (chave, nome, o que conta, tipo: contagem | percentual | minutos, se quanto menor melhor, e os filtros aceitos: funil, etapa). Use antes de create_goal.

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_goal_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds value by disclosing the shape of what comes back (key, name, counted quantity, type enum of contagem|percentual|minutos, lower-is-better flag, accepted filters). With no output schema present, that return-value disclosure is genuinely load-bearing.

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?

A single dense sentence enumerating return fields plus a short forward reference to create_goal — no filler, and the purpose is front-loaded before the usage note.

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 lookup with no output schema, the description does the heavy lifting by explaining what each metric record contains. It leaves minor uncertainty about whether the listed filters affect this call's output or are merely metadata about each metric.

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?

Zero parameters, so the schema baseline of 4 applies. The mention of accepted filters (funil, etapa) is slightly ambiguous since the tool takes no parameters — it reads as describing what the metrics support rather than inputs the agent supplies.

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?

States a specific verb and resource ("Lista as métricas que uma meta pode usar") and enumerates the returned fields — chave, nome, o que conta, tipo, direção e filtros aceitos. An agent immediately knows this is a reference/lookup tool for goal metric definitions, distinct from list_goals which returns goal instances.

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?

"Use antes de create_goal" gives explicit ordering guidance tied to a named sibling, which is exactly the context an agent needs to sequence goal creation. It stops short of stating when-not to call it or how it relates to update_goal, but the primary usage trigger is unambiguous.

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