Tomorrow Central: Cloud Cost Sentinel

Link a cloud account (needs a human)

create_cloud_connection

Start linking a cloud account so it can be scanned. provider is "aws", the only provider supported today; account_id is the 12-digit AWS account number.

This is a two-party flow and you cannot finish it alone — creating the read-only
IAM role requires the human's AWS credentials. Returns a `launch_url`.

Hand the human these instructions verbatim:
  1. Open the launch_url (a pre-filled CloudFormation quick-create link).
  2. Review the read-only role it creates, then click Create stack.
  3. Tell you when the stack says CREATE_COMPLETE.
Then call `verify_connection` with the returned connection_id. Verification fails
with a clear message until the role exists, so polling it every ~15 seconds is
safe and expected. No ARN or secret needs to be copied by anyone.

Input Schema

TableJSON Schema

Name	Required	Default
`label`	No
`region`	No	us-east-1
`provider`	No	aws
`account_id`	Yes

TDQS

A4.5/5.0

Behavior5/5

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

Discloses key behavioral traits: two-party flow requiring human AWS credentials, returns launch_url, verification progressively fails until role exists, no ARN/secret copy needed. Adds context beyond the sparse annotations, making the tool's behavior predictable.

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?

Well-structured with numbered instructions for human handoff and clear paragraphs. Every sentence adds value; not overly long given the complexity of the two-party flow.

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?

Given the two-party flow and no output schema, description covers return value (launch_url), next steps, and expected failure mode. Integrated with sibling verify_connection, making the tool's role in the workflow clear and 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?

Explains provider (only aws) and account_id (12-digit), but omits label and region entirely. With 0% schema coverage, this is a gap for those parameters; however, the required and provider params are well-defined, providing some semantic value.

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?

Clearly states 'Start linking a cloud account so it can be scanned' with specific details (provider is aws, account_id is 12-digit). Distinguishes from verify_connection by describing the two-party flow and subsequent step.

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

Usage Guidelines4/5

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

Provides clear workflow and sequencing (call verify_connection after stack creation), but does not explicitly state when not to use this tool or mention alternatives; the guidance is strong but lacks exclusionary context.

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

All Tomorrow Central: Cloud Cost Sentinel tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct resource and action: connection lifecycle (create, verify, get, list), job lifecycle (run, get status, get result), and findings (list). Even get_job_result and list_cost_findings are clearly differentiated as raw vs. analyzed data, and whoami/list_tools_available serve metadata purposes.

Naming Consistency4/5

Most tools follow a consistent verb_noun pattern (create_, get_, list_, run_, verify_). The only outlier is 'whoami', which breaks the pattern but is a recognizable convention for account identification. Overall naming is predictable and readable.

Tool Count5/5

With 10 tools, the set is well-scoped for a cloud cost scanning platform. Each tool serves a clear purpose in the connection-scan-result workflow, with no redundancy or bloat.

Completeness3/5

The core scan workflow is covered (connect, verify, scan, get job, get findings), but there are notable gaps: no tool to delete/disconnect a cloud account, and no way to list past jobs or retrieve results without a prior job_id. These missing lifecycle/history operations could force agents to rely on external state or fail when context is lost.

Resources

Need Help?