Skip to main content
Glama

finance

Goals: List goals

list_goals
Read-onlyIdempotent
    List the user's financial goals.

    Default scope: active + completed goals (cancelled goals are
    hidden by default to avoid cluttering responses with abandoned
    targets, which accumulate over time). Pass
    ``include_cancelled=True`` or an explicit ``status="cancelled"``
    to see them.

    Args:
        status: Filter by a single status — "active", "completed",
            or "cancelled". When provided, ``include_cancelled``
            is ignored.
        include_cancelled: If True (and ``status`` is None), include
            cancelled goals in the default active+completed listing.
        limit: Maximum number of goals to return (default: 50, max: 200).
        offset: Number of goals to skip for pagination (default: 0).

    Returns:
        List of goals with progress info, plus ``total_count`` /
        ``has_more`` / ``offset`` / ``limit`` pagination metadata.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
offsetNo
statusNo
include_cancelledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already establish read-only, idempotent, and non-destructive behavior, and the description adds substantial behavioral context: cancelled goals are hidden by default to avoid clutter, include_cancelled and status interact with a defined precedence, and pagination metadata is returned. This clearly exceeds what annotations alone provide.

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?

The description is front-loaded with the core purpose and then provides dense, useful parameter and return-value documentation. Every section earns its place, and there is no redundant repetition of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 appropriately explains what the tool returns: a list of goals with progress info plus pagination metadata. It also covers default scoping, cancellation handling, and all parameter semantics. For a read-only listing tool, this is complete enough for an agent to invoke it correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden of explaining the parameters. It compensates thoroughly by defining status values ('active', 'completed', 'cancelled'), explaining the include_cancelled/status precedence, and adding limit default/max and offset pagination details that are absent from the schema.

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 clearly states the action and resource: 'List the user's financial goals.' It also adds useful scoping detail about active/completed/cancelled goals. However, it does not explicitly distinguish itself from sibling tools like list_shared_goals or list_goal_plans, so it falls short of full sibling differentiation.

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?

The description gives clear guidance on when to use status vs include_cancelled and explains the default behavior, so an agent knows how to adjust the call. It does not explicitly discuss when to prefer this tool over related list tools, but the context is clear enough for most goal-listing scenarios.

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