Clarifyprompt-MCP

register_platform

Instructions

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "category": "<category>",
      "label": "<label>",
      "description": "<description>"
    },
    "name": "register_platform"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Unique platform ID (lowercase, alphanumeric with hyphens)
`category`	Yes	Category this platform belongs to
`label`	Yes	Human-readable platform name
`description`	Yes	Short description
`syntax_hints`	No
`instructions`	No
`instructions_file`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.6.8Jun 2, 2026

changedInput schema / properties / description / description

Previous value: -"Short description of the platform"New value: +"Short description"

changedInput schema / properties / id / description

Previous value: -"Unique platform ID (lowercase, alphanumeric with hyphens, e.g. 'my-llm')"New value: +"Unique platform ID (lowercase, alphanumeric with hyphens)"

removedInput schema / properties / instructions / description

Removed value: -"Inline instructions for prompt optimization on this platform"

removedInput schema / properties / instructions_file / description

Removed value: -"Path to a .md file with detailed instructions (relative to config dir's instructions/ folder, or absolute)"

changedInput schema / properties / label / description

Previous value: -"Human-readable platform name (e.g. 'My Custom LLM')"New value: +"Human-readable platform name"

removedInput schema / properties / syntax_hints / description

Removed value: -"Platform-specific syntax hints (e.g. ['system prompts', 'JSON mode'])"

AddedMar 12, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'register a new platform' without mentioning side effects (e.g., overwriting an existing ID), authentication needs, or any implications. This is insufficient for safe invocation.

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?

The description is a single sentence, which is concise. It covers the core purpose without extra words. However, given the tool's complexity, slightly more structure (e.g., listing key prerequisites) could improve clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks important context such as return values (no output schema), error conditions, and post-registration effects. For a tool with 7 parameters and no annotations, this is insufficient to ensure correct usage.

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 mention any parameters or their roles. With a schema coverage of 57%, the description adds no value beyond what the schema provides. The three undocumented parameters (syntax_hints, instructions, instructions_file) are left entirely 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?

The description clearly states the verb (register) and resource (new custom AI platform for prompt optimization). This distinguishes it from sibling tools like update_platform and unregister_platform, making the purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives such as update_platform or unregister_platform. There is no context about prerequisites or suitable scenarios, leaving the agent uncertain about selection.

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