Skip to main content
Glama

winrm_host_delete

DestructiveIdempotent

Deletes a saved WinRM host from the inventory by name, optionally scoped, so stale or unused host entries can be removed.

Instructions

Delete a saved WinRM host.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
scopeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — it does not say what happens to a host that is missing the target, whether removal is reversible, or whether in-memory sessions are affected.

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?

A single front-loaded sentence with zero filler; the action and target appear immediately. Brevity is appropriate, though it tips into under-specification rather than efficient density.

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?

For a destructive mutation with an output schema and an undocumented optional "scope" parameter, the definition is too thin. It omits prerequisites, what identifies the target when "scope" is unset, and the failure behavior for unknown host names.

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?

Schema description coverage is 0%, so the description would need to carry the parameter meaning, and it does not: neither the required "name" nor the optional "scope" (default null) is mentioned. "Saved WinRM host" hints that "name" identifies a stored entry, but the purpose and interaction of "scope" are entirely undocumented.

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 gives a specific verb ("Delete") and resource ("a saved WinRM host"), which cleanly separates it from sibling read/write tools like winrm_host_list, winrm_host_get, winrm_host_save, and winrm_host_update. It stops short of explicitly naming those siblings, but the CRUD verb makes the operation 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?

There is no when-to-use guidance: nothing states that this permanently removes a stored host entry rather than modifying it, and no alternative (e.g., winrm_host_update for modifying settings) is offered. An agent must infer all routing decisions from the verb alone.

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