Skip to main content
Glama

delete_balance

Removes balance entries for a specified period. Provide a category to delete a single entry, or omit to clear all entries for that period.

Instructions

Delete balance entries for a period. If category is provided, only that single entry is removed; otherwise all entries for the period are deleted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodYesYYYY-MM
typeNoRequired when category is provided
sub_typeNoRequired when category is provided
categoryNoSpecific category — if omitted, deletes all entries for the period
Behavior3/5

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

No annotations are provided, so the description must fully disclose behavior. It covers the conditional deletion logic but lacks details on side effects, permissions required, reversibility, or return value. The behavioral context is incomplete.

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 two sentences, efficiently conveying the core purpose and conditional logic with no extraneous words. It is well-structured and front-loaded.

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?

Given the tool has 4 parameters, conditional behavior, and no output schema, the description is adequate but minimal. It lacks details on return format, prerequisites (e.g., period must exist), or risk warnings for bulk deletion. Not fully 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?

Schema coverage is 100%, so the schema already describes each parameter. The description adds little new meaning beyond restating the conditional behavior for category. It does not enhance understanding significantly.

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 clearly states the verb 'delete' and resource 'balance entries', and distinguishes between single-entry deletion (with category) and bulk deletion (all entries for the period). This differentiates it from sibling tools like delete_flow or delete_txn.

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?

The description implies when to use (delete balance entries) and gives conditional behavior, but does not explicitly state when not to use or provide alternative tools for other record types. The agent must infer usage from context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/evan-moon/firma'

If you have feedback or need assistance with the MCP directory API, please join our Discord server