Skip to main content
Glama

ADS Beast

list_tasks

Read-only

Return the team tasks recorded in ADS Beast with their status, priority, assignee and the client they belong to.

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
limitNoPage size. Clamped into 1..500 before the request. A page is also cut to fit the response size limit; when the reply has has_more = true, call again with offset = next_offset.
offsetNoPagination offset. The reply carries total.
statusNoRestrict to one status.
priorityNoRestrict to one priority.
client_idNoRestrict to one client.
assigned_toNoUsername of the assignee.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the returned field set and the source system name; it says nothing about pagination behavior, permissions, or result volume beyond what the schema already documents.

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

Conciseness4/5

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

A single front-loaded sentence with no wasted wording. It is efficient, though it spends its only clause on return fields rather than on usage routing.

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 read-only, fully-annotated, fully-documented six-parameter list tool with no output schema, the description supplies the returned field set, which usefully stands in for the missing output schema. Only routing guidance toward sibling list tools is absent.

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

Parameters3/5

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

Schema description coverage is 100%, with limit, offset, and the two enums fully documented including clamping and has_more/next_offset semantics. The description mentions no parameters at all, so the baseline 3 applies.

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 specific verb (return) and resource (team tasks in ADS Beast) and enumerates the fields returned: status, priority, assignee, client. That distinguishes it from siblings like list_clients or list_alerts, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use guidance, no exclusions, and no mention of alternatives among the many other list_* tools. An agent must infer from the resource name alone that this is the task-listing endpoint.

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.