Skip to main content
Glama
Sign In
papers

papers

by coalesc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_trial_balance

Retrieve the trial balance for an engagement by ID, optionally as of a specific date, to provide the financial data needed for analysis and review.

Instructions

Read a trial balance for an engagement

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": {
      "engagement_id": "<engagement_id>"
    },
    "name": "get_trial_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoISO 8601 date; defaults to period end
engagement_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description must carry the full behavioral disclosure burden. 'Read' signals a non-mutating operation, but the description gives no detail about return contents, error behavior, data scope, or defaults such as as_of behavior.

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 clear sentence with no wasted words. The key action and target resource are front-loaded, making it easy to scan.

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?

The tool has no output schema and no annotations, so the description is responsible for explaining what the agent can expect. It does not describe the trial balance contents, return format, or behavior of the optional as_of parameter, leaving notable gaps for a tool this minimal.

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

Parameters2/5

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

Schema description coverage is only 50%, with engagement_id left undocumented. The description adds no parameter-level meaning beyond implying engagement context, so it does not compensate for the missing schema coverage.

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 clearly identifies the verb ('Read') and resource ('a trial balance for an engagement'), so an agent can understand the core function. It stops short of a 5 because it does not explicitly distinguish itself from sibling tools like get_capabilities or list_engagements.

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 gives no guidance on when to choose this tool over alternatives, nor any exclusions or prerequisites. The intended use is inferable from the name and phrasing, but the tool itself does not state it.

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