RetailHardHat

Get Budget Category Details

get_budget_category_details

Read-onlyIdempotent

Use this to explain which actual budget line items contribute to a RetailHardHat source/category total or overrun. Read-only drill-down of the current authorized portfolio; distinguishes missing actuals from zero and does not combine overlapping sources.

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": {
      "sourceId": "<sourceId>",
      "category": "<category>"
    },
    "name": "get_budget_category_details"
  }
}

Input Schema

Name	Required	Description	Default
`category`	Yes	Exact configured category label from that source's summary.
`sourceId`	Yes	Exact sourceId from an authorized budget summary.

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A5/5.0

Behavior5/5

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

While annotations confirm it is read-only, the description adds significant behavioral context not in the schema or annotations. Specifically, it discloses how the tool handles data ambiguities ('distinguishes missing actuals from zero') and data aggregation rules ('does not combine overlapping sources').

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 definition is highly concise, using only two sentences. Every clause serves a specific, valuable purpose, front-loading the core functionality and immediately addressing complex behavioral constraints.

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

Completeness5/5

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

Given that the underlying data concerns financial auditing and potential data discrepancies (missing actuals vs. zero), the description provides all necessary behavioral guarantees to the agent. There are no critical missing pieces of information required for correct usage.

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

Parameters5/5

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

Though the schema coverage is 100%, the description adds vital domain constraints to the parameters, specifying that the category must be the 'Exact configured category label' and the sourceId must be from an 'authorized budget summary.' This context is critical for successful invocation.

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 identifies the function (explain line item contributions) and the scope (RetailHardHat source/category total or overrun). It successfully differentiates this tool from other potential aggregation functions by stating it 'does not combine overlapping sources.'

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

Usage Guidelines5/5

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

The tool provides explicit usage guidance by defining the scope of its operation ('current authorized portfolio') and detailing crucial functional constraints: it handles missing actuals differently from zero and avoids combining overlapping sources, which helps the agent understand its limitations.

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

All RetailHardHat tools Inspect

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

Need Help?