Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Where an architecture is allowed to run, and what that costs

where_can_this_run
Read-only

Apply requirements FIRST, then price only the regions that survive.

Use this when the question is WHERE something may or should run (data
residency, a jurisdiction to avoid, near its users, surviving a zone
failure), with or without what it would cost. Not for pricing one region
already chosen: that is `estimate_cost`, or `describe_workload` for a
workload in plain words.

`items` (the `estimate_cost` shape, not empty) and `constraints`
(`[{"constraint": "<id>", "value": "<value>"}]`) take ids from one
`list_cost_building_blocks` call with `of=["components", "constraints"]`,
then come straight here. If a location value is refused, the error lists
the valid values: retry with one of those.

The user does not have to describe the workload first. Location
requirements decide which regions are allowed whatever the architecture,
so pass the smallest one that fits what they said and state it as an
assumption. An architecture requirement (zone failure) applies only to the
components you pass: read `changes` and `unmet`, and never report anything
in `unmet` as met.

Only requirements in the catalogue's `constraints` are checked.
`users_near` narrows to a broad area such as `emea`, not to a latency
figure: for a millisecond target, say plainly that it was not checked.

`options` are allowed regions that price every line, cheapest first.
`cannot_run_this` are allowed but do not sell part of it. `excluded` failed
a requirement, each with the reason. `cost_of_requirements` splits the
premium into location and the architecture changes it forced.

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": {
      "items": "<items>",
      "constraints": "<constraints>"
    },
    "name": "where_can_this_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNoOnDemand
itemsYes
regionsNo
constraintsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

The readOnlyHint annotation only tells the agent this is a safe read; the description adds substantially more — that only catalogue constraints are checked, that users_near narrows to a coarse area rather than a latency figure, that unmet items must never be reported as met, and how refusals surface as errors listing valid values. It also documents the result sections (options cheapest-first, cannot_run_this, excluded with reasons, cost_of_requirements) despite no output schema.

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?

It is long but front-loaded with the decisive rule (requirements first, then price), and each short paragraph has a single focus — routing, inputs, assumption handling, constraint limits, outputs. A few sentences pack two ideas, but no line is filler; nothing could be cut without losing routing or behavioral information.

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?

For a four-parameter, multi-purpose tool with no output schema and 0% schema description coverage, the description supplies the missing input formats, the cross-tool prerequisite, the assumption-handling policy, and a full map of the return structure. An agent has everything needed to call it and interpret the result without guessing.

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?

Schema coverage is 0%, so the description must carry the load, and it does well for the two required parameters: items is described as the estimate_cost shape and non-empty, and constraints is given the exact literal form with an example and where its ids come from. However, `term` (default OnDemand) and the `regions` input are left unexplained — regions in particular risks being confused with the `options` output, so the coverage is strong but not complete.

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 states a specific operation — apply requirements, then price surviving regions — and the second paragraph pins the scope as "WHERE something may or should run." It explicitly names what it is not (estimate_cost for a single chosen region, describe_workload for plain-language workloads), so an agent can route correctly without opening any schema.

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 gives explicit when-to-use triggers (data residency, jurisdiction to avoid, proximity to users, zone-failure survival), explicit exclusions routing to two named siblings, and even the prerequisite workflow: get ids from one list_cost_building_blocks call with of=["components","constraints"] and pass them here. Recovery guidance for refused location values is included.

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