Skip to main content
Glama
Sign In
COR MCP Server

COR MCP Server

by fxckcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cor_delete_client

Delete a client from the system by providing its unique client ID.

Instructions

Delete a client.

Args: client_id: The client ID

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": {
      "client_id": "<client_id>"
    },
    "name": "cor_delete_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Lacking annotations, the description should disclose behavioral traits. It only states 'Delete a client' without indicating irreversibility, cascading effects, or permission requirements. This is insufficient for a destructive operation.

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 very short and to the point. It follows a docstring format with Args section, but could be more front-loaded. No superfluous content.

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?

Despite a simple operation and presence of an output schema, the description omits details about deletion behavior (permanent?, confirmation?), error handling, or return value. It feels incomplete for safe agent use.

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 for parameter 'client_id' is 'The client ID', which adds minimal value beyond the schema's title. With 0% schema description coverage, more detail was expected (e.g., format, source).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Delete a client' which clearly identifies the verb and resource. It distinguishes from sibling tools like create_client or update_client, though it adds no further context.

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?

No guidance on when to use this tool versus alternatives, no prerequisites, side effects, or conditions for use are mentioned.

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

Deploy Server

Other Tools