Clarifyprompt-MCP

unregister_platform

Remove a custom platform or clear instruction overrides on a built-in platform.

Instructions

Remove a custom platform, or clear instruction overrides on a built-in.

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>"
    },
    "name": "unregister_platform"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`category`	Yes
`remove_override_only`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.6.8Jun 2, 2026
- removedInput schema / properties / category / description
```
Removed value: -"Category the platform belongs to"
```
- removedInput schema / properties / id / description
```
Removed value: -"Platform ID to remove"
```
- removedInput schema / properties / remove_override_only / description
```
Removed value: -"If true, only remove instruction overrides (for built-in platforms)"
```
AddedMar 12, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations exist, so the description should fully disclose behavior. It mentions removal and clearing overrides but omits side effects, permission requirements, or consequences.

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, efficient sentence, but it could add more detail without becoming overly verbose.

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?

Given no annotations, no output schema, and 0% schema coverage, the description is insufficient. It lacks information on return values, error conditions, and post-removal effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description provides no explanation of the three parameters (id, category, remove_override_only) or their roles.

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 tool removes a custom platform or clears instruction overrides on a built-in platform, distinguishing its purpose from siblings like register_platform and update_platform.

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

Usage Guidelines3/5

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

The description implies when to use (removing or clearing overrides) but lacks explicit guidance on when not to use or alternatives among the listed siblings.

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