Centia MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

deleteClient

Remove an OAuth client by providing its ID. Use this to delete unused or compromised clients from your Centia configuration.

Instructions

Delete OAuth client(s).

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Id of client

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.9May 26, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description should disclose behavioral traits like irreversibility, authorization needs, or side effects. It only states the action, leaving safety and consequences unspecified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence), which is concise but at the cost of missing critical information. It is appropriately sized for a simple tool but lacks depth.

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

Completeness3/5

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

Given the simplicity (one param, no output schema), the description is minimally adequate but incomplete for safe autonomous use. It omits details about behavior, errors, and return values.

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

Parameters3/5

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

The single parameter 'id' is fully described in the schema with 100% coverage. The description adds no extra semantics or constraints beyond what the schema already provides.

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 'Delete OAuth client(s).' clearly states the action and resource, and distinguishes it from sibling tools that operate on other resources. However, the plural 'client(s)' is slightly ambiguous given the schema expects a single client ID.

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 is provided on when to use this tool versus alternatives like deleteColumn or deleteUser. There are no prerequisites or contextual hints for an agent to decide appropriateness.

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