Skip to main content
Glama
test-task-server

test-task-server

by shazamlll

List test tasks

list_test_tasks

Retrieve all submitted test tasks and their current statuses to monitor progress and review deterministic pass/fail outcomes.

Instructions

List all submitted test tasks with their current statuses.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses that results span all submitted tasks and that each carries a current status, which is useful, but it says nothing about ordering, result volume, pagination, or whether tasks in every state (pending/completed/failed) are included.

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 filler. It is efficient, though the brevity leaves the behavioral gaps noted above unaddressed rather than wasted.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and no output schema, the description is the only place an agent can learn what comes back, and it covers that minimally (a set of tasks plus statuses). Details such as ordering, pagination, and which statuses appear are missing for a listing tool expected to return potentially many records.

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 schema defines zero parameters, so there is no parameter meaning for the description to add. Baseline 4 applies; nothing in the description misleads about 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?

"List all submitted test tasks with their current statuses" names a specific verb (List), a specific resource (test tasks), and the scope (all submitted). It does not, however, distinguish itself from the sibling get_task_result, which an agent could plausibly reach for when looking for task status information.

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 only implied: "list all" suggests enumeration rather than single-task lookup, which weakly routes away from get_task_result. There is no explicit statement of when to prefer this over the sibling or of any preconditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools