Skip to main content
Glama
Sign In
k8scortex-mcp

k8scortex-mcp

by apatilgtn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_vpa_recommendation

Return VPA recommendation lower, target, and upper bounds for a workload in a given namespace and cluster.

Instructions

Returns VPA recommendation lower/target/upper bounds for a workload when available.

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": {
      "namespace": "<namespace>",
      "vpaName": "<vpaName>"
    },
    "name": "get_vpa_recommendation"
  }
}

Input Schema

NameRequiredDescriptionDefault
clusterNoTarget cluster name (default: 'default')
vpaNameYesVPA object name
namespaceYesNamespace

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.5/5.0
Behavior3/5

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

Mentions 'when available' hinting at conditional availability but does not explain behavior if unavailable (error vs empty). No annotations; description provides modest transparency about bounds but lacks details on prerequisites or side effects.

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?

Single sentence, no redundant information. Every word serves a purpose.

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?

No output schema, so description should explain return structure. It mentions bounds but not the format or what happens when data is unavailable. Adequate for a simple tool but could be more complete.

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%, so baseline 3 applies. Description adds no extra meaning beyond the schema's parameter descriptions; it does not clarify values or why cluster defaults to 'default'.

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

Purpose5/5

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

Description clearly states the verb ('returns'), resource ('VPA recommendation bounds'), and condition ('when available'). It is specific and distinguishes from siblings like 'get_resource_recommendations'.

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 explicit guidance on when to use this tool vs alternatives like 'get_resource_recommendations'. The description only states what it does, not context for selection.

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