Skip to main content
Glama
Infrawise

Infrawise

Official
by Infrawise

get_sku_optimizations

Retrieve rightsizing recommendations for overprovisioned Azure resources to reduce costs by selecting optimized SKUs.

Instructions

Retrieve rightsizing recommendations for overprovisioned resources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subscription_filterNoOptional subscription ID to filter results. When omitted, returns merged results across all accessible subscriptions.
Behavior3/5

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

The description implies a read-only operation but does not disclose any behavioral traits beyond the basic purpose. With no annotations, it carries the full burden but is acceptable for a simple retrieval tool.

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 with no waste, front-loaded with the core purpose.

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?

Adequately describes the tool's purpose for a simple one-parameter retrieval, though lacking output schema details would be a minor gap.

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 clear description for the only parameter, so the description adds no additional meaning beyond the schema.

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?

The description uses a specific verb 'Retrieve' and resource 'rightsizing recommendations for overprovisioned resources', clearly differentiating from siblings like get_general_recommendations and get_idle_resources.

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 on when to use this tool vs siblings; the description only states what it does without context on alternatives or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Infrawise/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server