Skip to main content
Glama

List purposes

list_purposes
Read-only

The purpose presets resolve accepts: named jobs such as reading receipts or a coding agent, each with the task, needs and budget it stands for. 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_purposes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description adds one genuine behavioral fact beyond them: 'Free,' i.e. no cost to call. It says nothing about whether the catalog is static or how many entries come back, which is the remaining useful detail for a lookup tool.

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 sentence with the resource identified first, examples second, and the shape of each returned item last — all of it earning its place. Nothing is padded or restated from the title.

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 describing what each entry contains (task, needs, budget) plus a concrete example, which is enough to know what comes back. It stops short of saying whether the list is fixed in size or ordered, and does not explicitly frame itself as the discovery step before `resolve`.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. It correctly spends no words on inputs.

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 identifies the resource precisely: the set of purpose presets that the `resolve` tool accepts, with concrete examples (reading receipts, a coding agent). That ties it to a specific sibling and separates it from `list_models` or `get_vocabulary`. It never states the verb outright ('lists'/'returns'), relying on the name and title for that.

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?

Usage is strongly implied: an agent learns these are the valid inputs for `resolve`'s purpose argument, so calling this before `resolve` is the obvious path. However, there is no explicit when-to-use directive, no statement that this is a prerequisite/discovery call, and no exclusions versus `get_vocabulary` or `plan`.

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