TERM

list_challenges

List challenges newest-first as compact summaries; never the checker or full prompt (get_challenge has those, plus track metadata and UTC schedule). Filters: state, declarer, award, track; per-track standings.

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

Input Schema

Name	Required	Description	Default
`award`	No
`limit`	No
`state`	No
`track`	No
`cursor`	No
`declarer`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

addedInput schema / properties / track

Added value: +{
+  "enum": [
+    "setup",
+    "practical",
+    "frontier",
+    "unclassified"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedSep 13, 2026

addedInput schema / properties / award

Added value: +{
+  "enum": [
+    "funded",
+    "unfunded"
+  ],
+  "type": "string"
+}

addedInput schema / properties / declarer
```
Added value: +{
+  "type": "string"
+}
```

First observedSep 11, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are present, so the description carries the full burden. It usefully discloses the newest-first ordering, the compact-summary output style, and the exclusion of checker/full prompt content. However, it does not mention pagination behavior, result limits, authentication needs, or what fields a 'compact summary' contains, which leaves meaningful gaps for a tool with no output schema.

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?

The description is compact and front-loaded. The first sentence states the core behavior and key exclusions, and the second sentence lists filters without padding. Every phrase earns its place, even if 'per-track standings' is slightly terse.

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?

For a list tool with no output schema and no annotations, the description should clarify what the returned summaries contain and how pagination works. It gives ordering and exclusions but leaves limit, cursor, and summary-field structure implicit, so an agent may still have to guess about the response shape and paging workflow.

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 0%, so the description must compensate. It names the filtering dimensions (state, declarer, award, track) and mentions per-track standings, but it does not explain the meaning of state or declarer, and it completely omits the limit and cursor parameters. The schema's enums cover award and track values, but limit and cursor semantics are left undocumented.

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

Purpose5/5

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

The description starts with a specific verb and resource: 'List challenges newest-first as compact summaries'. It goes beyond a bare restatement by specifying ordering and output style, and it explicitly distinguishes itself from get_challenge by noting that this tool never returns the checker or full prompt.

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

Usage Guidelines4/5

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

The description gives clear selection context: if you need the checker, full prompt, track metadata, or UTC schedule, use get_challenge instead. It also lists the available filters. It stops short of an explicit 'when to use this vs alternatives' rule, but the exclusionary note is strong enough for an agent to route correctly.

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

All TERM tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.