Skip to main content
Glama

decommission_candidates

Read-onlyIdempotent

Identifies servers with no live workload within a stale period as decommission candidates, reports reasons, and marks unknown workloads as blocked instead of eligible.

Instructions

Servers with no live workload, with reasons. Servers whose workload is unknown are listed as 'blocked', never as candidates.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "decommission_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
stale_daysNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuinely non-obvious classification behavior beyond the annotations: unknown-workload servers are surfaced as 'blocked' and excluded from candidates, which prevents an agent from misreading an incomplete result as a safe-to-decommission list.

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?

Two short sentences, front-loaded with the primary output and followed by the exclusion rule; nothing is padding. Minor ambiguity remains in 'with reasons', which does not say whether reasons are per-server fields or a summary, but the phrasing is efficient overall.

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?

An output schema exists, so return structure needn't be explained, and the safety profile is covered by annotations. The remaining gap is the undocumented stale_days threshold, which directly affects which servers are reported and is essential for correct invocation of this otherwise simple, single-parameter tool.

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 single parameter, stale_days (default 90), has 0% schema description coverage and is not mentioned anywhere in the description. The agent gets no explanation of what staleness is measured against or how lowering/raising the threshold changes candidacy, so the description fails to compensate for the coverage gap.

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?

States a specific verb and resource: it returns servers with no live workload, plus the reasons for each. It also sharpens the boundary by saying unknown-workload servers appear as 'blocked', not as candidates. It is clear and distinct within the sibling set, though it never names an alternative tool for adjacent questions (e.g. root_cause_candidates).

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?

Usage is implied by the name and the candidate-vs-blocked distinction, so an agent can infer this is the entry point for decommission planning. However, there is no explicit when-to-use or when-not-to-use statement, and no alternative sibling is named for cases the caller actually wants blocked servers only or impact analysis.

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