Clarifyprompt-MCP

list_traces

List recent optimization traces from prompt transformations. Use to review history and summaries of processed prompts.

Instructions

List recent optimization traces from the local tracer. Summary only; use get_trace for full records.

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

Input Schema

Name	Required	Description	Default
`day`	No	UTC day YYYY-MM-DD; defaults to the most recent day with data
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.6.8Jun 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description alone must convey behavioral traits. It notes 'recent' (though undefined) and 'from the local tracer,' but does not disclose ordering, pagination behavior, or whether the operation is read-only. The suggestion to use get_trace for full records adds some context.

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?

Two sentences, front-loaded with the primary purpose and then usage guidance. Every sentence adds value without redundancy or fluff.

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 list tool with two optional parameters and no output schema, the description covers the main purpose and links to a more detailed sibling. It could be improved by clarifying what 'recent' means, but overall it's adequately complete given the tool's low complexity.

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?

The description does not add any meaning beyond the input schema. Schema coverage is 50% (only 'day' has a description). The parameter 'limit' lacks a description in both schema and tool description, leaving its purpose and constraints unexplained.

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?

Description clearly states 'List recent optimization traces' (specific verb+resource) and distinguishes from sibling 'get_trace' by noting 'Summary only; use get_trace for full records.' This explicitly differentiates the tool's purpose.

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?

Description provides clear guidance to use 'get_trace' for full records, indicating when to use this tool vs. an alternative. However, it does not specify when not to use this tool (e.g., if more than recent data is needed) or other contextual triggers.

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