Skip to main content
Glama
Sign In
cloudscope-mcp

cloudscope-mcp

by alexpota
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Budget Status

check_budgets
Read-onlyIdempotent

Check budget status by comparing current spend against limits, including forecast and overage risk, for Azure or GCP accounts.

Instructions

Check budget status: current spend vs limit, percentage used, forecast, and overage risk. For GCP, requires GCP_BILLING_ACCOUNT_ID to be set.

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

Input Schema

NameRequiredDescriptionDefault
providerNoCloud provider to query (azure or gcp)azure

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.3
  2. Removedv0.3.1
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so safety is covered. The description adds the GCP prerequisite and mentions the type of data returned (forecast, overage risk), providing useful behavioral context beyond annotations.

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?

Two sentences: first states the purpose concisely, second adds a critical prerequisite. No unnecessary words, front-loaded with key 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?

The description covers the tool's purpose and key conditions clearly. With no output schema, it lists the types of data returned (spend vs limit, percentage, forecast, overage risk). Could mention relationship to cost tools, but adequate for a simple read tool with annotations.

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% with the parameter 'provider' fully described. The description adds no additional meaning beyond the schema, only a conditional usage note. Baseline of 3 applies as per guidelines.

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 'Check' and resource 'budget status', clearly listing the metrics (current spend vs limit, percentage used, forecast, overage risk). None of the sibling tools mention budgets, so it distinguishes well.

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?

The description provides a clear condition for GCP usage (requires GCP_BILLING_ACCOUNT_ID) but does not explicitly state when to use vs alternatives like cost summary or forecasts. The context is clear but lacks exclusions.

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

Deploy Server

Other Tools