Skip to main content
Glama

List the goals

list_goals
Read-only

The goals an answer depends on (cost, depth, where a model's maker is based, where data may stay, languages, the kind of data, the accounts already held), each with one question to ask the user, the options to offer and the parameters each answer is sent as, and the rules for asking. Call it once when planning an app. Free.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds value beyond that by disclosing that results are static reference data with no arguments, that calling is free, and that it should be invoked exactly once rather than per-question. With no output schema, the return-shape summary (question + options + parameter mapping + asking rules) is genuinely useful context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It leads with a bare noun phrase rather than an action, then packs seven parenthetical examples into a single dense sentence with nested clauses before the two short operational sentences. Every element is substantive, but the structure buries the actionable guidance ('call once, free') at the end.

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 listing tool with no output schema, the description supplies what an agent needs: what the records are, what fields they carry, and the intended call pattern. Minor omission is how this relates to plan/list_purposes in an overall workflow.

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 zero parameters, so the schema-based baseline of 4 applies. The description does mention 'the parameters each answer is sent as', but that describes output content rather than input semantics, so it neither helps nor misleads on parameters.

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 specifies the resource precisely by enumerating what a 'goal' is (cost, depth, model-maker location, data residency, languages, data kind, existing accounts) and what each record carries (a question, options, the parameter each answer maps to). It is clear what the tool returns, though it never uses an explicit verb and does not name a sibling such as list_purposes to disambiguate 'goals' vs 'purposes'.

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?

"Call it once when planning an app" gives a concrete trigger and a cardinality constraint, and "Free" signals the cost of calling. There is no explicit when-not or named alternative, so an agent must infer that list_purposes/plan serve different phases.

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