Skip to main content
Glama
cloudsketch-mcp

cloudsketch-mcp

Official

Check CloudSketch AI credits

check_credits
Read-only

Displays the CloudSketch AI plan and remaining API credits for today and the current month for the token's account.

Instructions

Show the CloudSketch AI plan and how many credits are left today and this month for the API token's account.

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_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The readOnlyHint and openWorldHint annotations already establish that this is a safe read against an external service. The description adds useful behavioral context by specifying that the result includes the plan and credit balances for today and this month, scoped to the API token's account. It does not discuss auth or rate-limit behavior, but that is a minor gap for a simple read-only status tool.

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?

The description is a single well-formed sentence with no filler. The most important information, what the tool shows and which account it applies to, is front-loaded.

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 simple zero-parameter read-only tool with annotations and no output schema, the description is largely complete because it explains the returned information and account scope. It could be slightly stronger with a brief usage note about when an agent should check credits, but no critical invocation detail is missing.

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 tool has zero parameters, so there is no parameter semantics to clarify. The baseline score for a zero-parameter tool is 4, and the description appropriately does not invent parameter details.

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 states a specific verb and resource: it shows the CloudSketch AI plan and remaining credits for today and this month. It also scopes the result to the API token's account, which helps distinguish it from generation or listing tools. However, it does not explicitly contrast itself with any sibling tool.

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

Usage Guidelines2/5

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

The description explains what information is returned but gives no explicit when-to-use guidance, prerequisites, or alternatives. It is implied that an agent should call it to check credit balances, but there are no usage rules such as when to check before generating diagrams or how to handle insufficient credits.

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