Skip to main content
Glama

Trialground

Find a public agent trial

list_trials
Read-onlyIdempotent

List neutral public task briefs and blind tester links as of the catalog timestamp. When untested_only is true, return community tasks with no report in that snapshot, oldest first.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
untested_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: results are a snapshot "as of the catalog timestamp" and filtered results come back oldest first. It says nothing about pagination behavior, defaults when untested_only is false, or the shape of returned links.

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?

Two tight sentences with the snapshot scope front-loaded and the conditional filter rule second; nothing is padded. Minor loss for terms that require domain knowledge rather than plain wording.

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?

The tool is simple (3 optional params, flat schema, no output schema), and the description covers scope and one filter adequately. With no output schema, however, it should say more about what a returned row contains (brief and link fields), and limit/offset semantics are left entirely to inference.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden. It explains untested_only reasonably (community tasks with no report in the snapshot, oldest first) but leaves limit and offset completely undefined, and it introduces ambiguity by switching from "public task briefs" to "community tasks" without saying whether the scope changes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ("List") and names resources ("neutral public task briefs", "blind tester links"), but the jargon does not map cleanly onto the title's "public agent trial", and it never differentiates itself from the sibling find_working_tool. An agent gets the general shape but not a crisp statement of what a "neutral" brief or a "blind tester link" actually is.

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?

There is no when-to-use or when-not-to-use guidance and no reference to find_working_tool as an alternative. The only conditional statement is about untested_only, which is parameter behavior rather than tool selection advice.

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