Skip to main content
Glama

studio_update_balance

Refresh a manually reported credit balance for a production account using a supplied credit estimate without implying live verification.

Instructions

Refresh manually reported credit balance, without claiming live verification.

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": {
      "accountId": "<accountId>",
      "creditEstimate": "<creditEstimate>"
    },
    "name": "studio_update_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNo
accountIdYes
creditEstimateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses only a semantic caveat about verification and says nothing about whether the update overwrites an existing balance, whether it requires prior registration, whether it is idempotent, or what it returns despite the name 'update' implying a mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no redundant phrasing, but brevity here comes at the cost of clarity rather than from efficiency. The one caveat clause is front-loaded into the only slot where the actual operation should be explained.

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

Completeness2/5

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

A mutating tool with two required and one optional undocumented parameter, no annotations, and no output schema needs far more than one elliptical sentence. Key facts an agent would need before calling it, such as permission requirements, side effects, and the effect of 'enabled', are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must compensate and does not. It never explains what accountId refers to, what units or meaning creditEstimate carries, or what toggling the optional 'enabled' boolean does.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'refresh' and resource 'credit balance' are identifiable, but the qualifier 'manually reported' is ambiguous: it is unclear whether the tool manually reports the balance or merely refreshes a balance that was manually reported. The trailing clause 'without claiming live verification' gestures at intent without pinning down the operation.

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?

No when-to-use guidance is given: no prerequisites, no conditions that select this over alternatives, and no statement of when refreshing is inappropriate. The 'without claiming live verification' caveat hints at a distinction from some other verification path but never names or describes it.

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