cmt-mcp

list_submissions

Fetch an author's CMT conference submissions and their statuses, optionally filtered by conference, to get a compact overview for tracking review progress.

Instructions

List the user's submissions with status.

conference: UrlSegmentName (e.g. 'MyConf2026'). If omitted, pulls submissions across ALL of the user's conferences. Returns a compact status overview (no abstract/files; use get_submission for those). Results are cached for 15 min; set refresh=true to force a live fetch.

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

Input Schema

Name	Required	Description	Default
`refresh`	No
`conference`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: it discloses result caching (15 min), the refresh override, the cross-conference default scope, and the compact shape of the payload (no abstract/files). It does not cover permissions/auth requirements, which is the main remaining gap.

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?

Front-loads the core action, then handles each parameter and the caveat in tight sentences with no filler. The line-wrapping and parenthetical style are slightly dense, but nothing is redundant.

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?

An output schema exists, so return values need not be re-explained, and the description correctly stops at describing result shape rather than schema. For a two-param, no-annotation read tool it covers scope, caching, and the alternative sibling, leaving only auth/permission context unaddressed.

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?

Schema description coverage is 0%, so the description must compensate and largely does: conference is documented as a UrlSegmentName with a concrete example and a default-scope rule, and refresh is explained as a cache-bypass flag. Format details are adequate; the only omission is whether conference accepts an ID versus a name beyond the single example.

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 and resource ('List the user's submissions with status') and immediately scopes what the result contains versus what it omits. It also distinguishes itself from the sibling get_submission by pointing there for abstracts/files, so an agent can differentiate without opening either schema.

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?

Gives clear conditions: omitting conference pulls submissions across ALL conferences, and get_submission should be used when abstract/file detail is needed. It also explains refresh=true as the escape hatch from the cache. It lacks explicit 'when not to use' guidance (e.g. vs get_delta), so it falls just short of the top band.

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

Deploy Server