Skip to main content
Glama
mcp-aws-explorer

mcp-aws-explorer

by hsooligan95

get_cost_summary

Summarize mock cloud costs by service for the current month and compare total spend against last month across AWS, Azure, GCP, or OCI mock datasets.

Instructions

Summarize mock cost by service for the current month, with the change versus last month.

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

Input Schema

NameRequiredDescriptionDefault
providerNoCloud provider to query: 'aws', 'azure', 'gcp', or 'oci'. All datasets are local mock data.aws

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it does disclose that the data is 'mock' and that output includes a month-over-month comparison, which is useful context. However, it says nothing about currency, units, aggregation level, or whether the summary spans all services regardless of provider — meaningful gaps for a reporting tool with zero annotation coverage.

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?

A single sentence that front-loads the verb and resource with no filler. Every clause (current month, prior-month delta) contributes scope information.

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?

For a one-optional-parameter read tool with no output schema, the description states both what is produced (per-service cost) and the comparison dimension (change vs last month), and flags the data as mock. Minor omissions around units and provider scope keep it from a 5.

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 description coverage is 100% and the single 'provider' parameter has an enum, a default, and an explicit description noting the data is mock. The prose adds no parameter meaning beyond the schema, so the baseline 3 applies.

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 names a specific verb ('Summarize') and resource ('mock cost by service') and scopes it to 'the current month' plus a month-over-month delta. The sibling tools (get_resource_detail, find_idle_resources, list_resources) are resource-oriented, so cost summarization is distinguishable, though the description never explicitly contrasts itself with them.

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: reach for this when you want an aggregated cost breakdown for the current month. There is no explicit when-to-use/when-not-to-use statement and no mention of an alternative for per-resource cost or historical periods, leaving routing to inference.

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