Skip to main content
Glama

Get Creative Credit balance

get_credit_balance
Read-onlyIdempotent

Return the organization Creative Credit wallet for this brand, plus this connection's remaining daily spend cap when the caller is a machine.

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": {
      "brand_id": "<brand_id>"
    },
    "name": "get_credit_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
brand_idYesBrand workspace id from list_brands
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
      +  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds a genuinely non-obvious behavioral trait — the daily spend cap is only returned when the caller is a machine — but it does not explain what the wallet actually contains (units, currency, expiry, or what happens with a zero balance), which matters because there is 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?

A single front-loaded sentence with no filler; the primary result (wallet) precedes the conditional secondary result (spend cap). The trailing 'when the caller is a machine' clause is slightly awkward but earns its place by flagging conditional output.

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

Completeness3/5

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

For a simple two-parameter read tool this covers the essentials, and the lack of an output schema is partly offset by naming the two returned values. However, the shape of the wallet (balance fields, units, currency) and any failure mode (no credits, unknown brand_id) are left unstated.

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%, including 'Brand workspace id from list_brands' for brand_id and an explanation of user_goal, so the baseline is 3. The description only reinforces brand scoping ('for this brand') and adds no format or constraint detail beyond the schema.

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?

States a specific verb ('Return') and a specific resource ('organization Creative Credit wallet') scoped to a brand, and adds a second concrete output (this connection's remaining daily spend cap). No sibling tool overlaps this resource, so the agent can distinguish it immediately.

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

Usage Guidelines3/5

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

Usage is only implied by the resource name: an agent would infer 'call this to check remaining credits.' There is no explicit when-to-use framing, no prerequisites (e.g. does the caller need admin rights to see the org wallet?), and no named alternative or exclusion.

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