Skip to main content
Glama
Sign In
testit-mcp-server

testit-mcp-server

by iampopovich
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

purge_configuration

DestructiveIdempotent

Permanently deletes an archived configuration by ID. Archive the configuration first, because this action is irreversible.

Instructions

Permanently delete an archived configuration. Irreversible; delete (archive) it first.

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": "purge_configuration"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesConfiguration UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description still adds real value by stating the operation is irreversible and requires the record to be archived first — a workflow constraint the annotations do not express.

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 short clauses, front-loaded with the destructive nature and followed by the precondition. No filler, no repetition of the name.

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?

A one-parameter destructive tool with rich annotations and no output schema needs little more than what is present: what it does, that it is irreversible, and the archive precondition. Only the error behavior (e.g., what happens if the config is not archived) is unaddressed.

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?

Schema coverage is 100% with a single documented `id` parameter, so the description need not restate it. It adds no detail about the identifier (format, source, how to obtain it), leaving the schema to do all the work — the correct baseline here.

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?

Specific verb+resource: "Permanently delete an archived configuration" tells the agent exactly what is removed and that it must already be archived, which separates it from the archive-style delete_configuration and from the restore_* path. It does not name those siblings explicitly, so it stops short of 5.

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?

"delete (archive) it first" is an explicit precondition that routes the agent to the archive step before purging, which is the key decision for this tool. There is no explicit when-not guidance or named alternative, so it is strong but not exhaustive.

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