Skip to main content
Glama

magne.tools

List tasks

list_tasks
Read-only

Every task in the catalog, grouped by area in catalog order: each task's name, slug, number of published tools and page URL.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the read-only, closed-world profile, and the description adds genuinely new behavioral detail: results are grouped by area and emitted in catalog order, with a defined per-item payload. It stops short of stating whether the list is exhaustive across pagination or how large the response can get.

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 front-loaded sentence with a colon introducing the payload fields — no filler, no repetition of the title, and the grouping/ordering facts come before the field list.

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 parameters, no output schema, and annotations already declaring the safety profile, the description supplies exactly the missing piece: the shape and ordering of the returned list. Nothing an agent needs to decide to call it or interpret the result is absent.

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 the description needs to disambiguate; the baseline applies. It correctly makes clear the listing is unconditional rather than filtered.

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?

States a clear verb and resource (list every task in the catalog) and enumerates the returned fields (name, slug, tool count, page URL). The task-level scope distinguishes it in practice from the tool-oriented siblings, but the description never explicitly contrasts itself with them.

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 phrase 'Every task in the catalog' implies this is the full-enumeration tool with no filtering, which is a usable hint, but there is no explicit when-to-use or when-not-to-use guidance and no mention of find_tools_for_task or search_tools as alternatives for a different question shape.

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