RooQuiz

list_forms

Read-only

Retrieve a paginated list of team forms in reverse chronological order, with optional filters by scene and title. Use to browse forms without loading question details.

Instructions

List the forms of the current team. Returned in reverse chronological order of creation, without question content (use get_form for details).

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

Input Schema

Name	Required	Description
`limit`	No	Items per page, default 20, max 100
`scene`	No	Filter by scene, optional
`titleContains`	No	Fuzzy match by title, optional

Output Schema

Name	Required	Description	Default
`items`	No	The page of forms (newest first)
`totalDocs`	No	Total forms matching the filter

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 3, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already mark this as read-only and non-destructive; the description adds genuinely useful behaviors: reverse-chronological order by creation and omission of question content. No contradiction with annotations was found.

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 conveys the core action, scope, ordering, and content limitation without filler or redundancy. Every word earns its place.

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 simple read-only list tool with an output schema and fully documented optional filters, the description is adequate: it covers scope, ordering, and content omission. Minor details like whether deleted forms are included are not critical for correct invocation.

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?

The input schema fully describes all three optional parameters (limit, scene, titleContains), so schema description coverage is 100%. The description adds no additional parameter-specific meaning, so the baseline of 3 applies.

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?

States a specific verb ('List'), resource ('forms'), and scope ('current team'), and explicitly notes it excludes question content and routes to get_form for details. This clearly distinguishes it from sibling get_form and makes its scope unambiguous.

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?

Explicitly points to get_form as the alternative when form details are needed, which gives a clear when-to-use signal. It does not mention other related siblings like list_templates, so differentiation from all alternatives is not fully covered.

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

Deploy Server