Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

List what can be priced and named

list_cost_building_blocks
Read-only

Everything the estimator can be asked about, by name: a lookup, not an answer.

Use this when you need the exact ids that `estimate_cost`,
`compare_architectures` and `where_can_this_run` take and do not have them.
They reject any name not listed here. `describe_workload` does not need it:
it takes the user's plain words.

Not as the answer to a question: it prices nothing and applies no
requirement. One call per conversation is enough. Narrow it with `of`
(`components`, `capabilities`, `archetypes`, `drivers`, `constraints`,
`regions`), then go straight on to the tool that answers. Each entry carries
the exact shape to pass it back in. Do not stop to ask the user for detail
that the next tool defaults or that you can state as an assumption.

If what the user described is not in here, say so plainly and say what IS
covered. An estimate assembled from the nearest parts, presented as the
thing they asked about, is worse than no estimate.

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

Input Schema

NameRequiredDescriptionDefault
ofNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real behavior beyond that: it prices nothing, applies no requirement, entries carry the exact shape to pass back, and it prescribes handling of uncovered requests instead of approximating. It does not discuss result size or truncation, which keeps it at 4 rather than 5.

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?

The lead line is front-loaded and the when/when-not structure is easy to scan. Some of the closing guidance ('Do not stop to ask the user...') is advisory padding for a lookup tool and could be trimmed without losing signal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by telling the agent what entries contain and how to feed them back into the next tool. Combined with the explicit failure-mode instruction for names not covered, an agent has everything needed to call this correctly and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single `of` parameter has zero schema description coverage and no enum, so the description must carry it — and it does, enumerating the accepted values (components, capabilities, archetypes, drivers, constraints, regions) and its narrowing purpose. It stops short of saying the values are exact-match or how an array of them is combined.

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 opening line gives a specific verb and resource ('Everything the estimator can be asked about, by name') and explicitly frames it as 'a lookup, not an answer.' It also names three sibling tools it serves and one (describe_workload) that does not need it, so an agent can place it precisely in the catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states when to use it (when you need exact ids for estimate_cost, compare_architectures, where_can_this_run and lack them), when not to (as the answer to a question), and how to scope it via `of`. It also caps usage ('one call per conversation is enough') and prescribes the follow-on step ('go straight on to the tool that answers').

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources