Skip to main content
Glama
Sign In

Red by Big Red Cloud

by io.github.BigRedCloud
OverviewDiscussionsAdmin

Multi-Company Nominal Account Report

brc_multi_company_nom_ac_report
Read-only

Returns a multi-company nominal-account report with period movements rather than monthly balances.

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": {
      "companyNames": "<companyNames>"
    },
    "name": "brc_multi_company_nom_ac_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyNamesYesThe company names to report on.
connectionRefNoOpaque Red connection reference returned by brc_confirm_company_connection. Pass this exact value on every later tool call when the MCP client rotates session ids (for example Vibe/Mistral). Keep reusing the same connectionRef after successful tool calls — do not start a new connection because a lookup returned empty or partial data. It is not an API key and does not contain credentials.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, and the description does not contradict them. The description adds output-level context (period movements) but does not disclose further behavioral traits such as pagination, connection reuse, or failure semantics; the useful connectionRef reuse note lives only in the parameter schema.

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 front-loaded sentence with no filler. It states the action, the resource, and the key qualifier efficiently.

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-only report, the description and schema are mostly sufficient, but there is no output schema and the return structure is only vaguely described as 'period movements rather than monthly balances.' Missing usage context and report shape prevent full completeness.

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 companyNames and connectionRef are already well documented in the input schema. The tool description adds no parameter-specific meaning beyond what the schema and title already convey.

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 states a specific verb ('Returns') and resource ('multi-company nominal-account report'), and adds a useful differentiator with 'period movements rather than monthly balances.' However, it does not explicitly contrast any sibling tool, so the differentiation from similar report tools is only implicit.

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?

No explicit 'use when' guidance or alternative tool is named. The phrase 'rather than monthly balances' implies this is intended for period-movement analysis, but the agent is left to infer when to select this over sibling reports like brc_grouped_nominal_accounts_report.

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

All Red by Big Red Cloud toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources