BR Intelligence

business_days

Brazilian business days (national holidays, including Carnaval and Corpus Christi; no state/municipal holidays). With only date: is it a business day and the next/previous one. With add: date after N business days. With end: business days between date (inclusive) and end (exclusive). Price: $0.003.

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": {
      "date": "<date>"
    },
    "name": "business_days"
  }
}

Input Schema

Name	Required	Description
`add`	No	Business days to add (negative subtracts).
`end`	No	End date YYYY-MM-DD to count business days.
`date`	Yes	YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 30, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does well: it specifies the holiday scope (national holidays including Carnaval and Corpus Christi, no state/municipal holidays), defines output per mode, and states the price. It omits edge-case behavior such as what happens if both add and end are provided, or how invalid dates are handled.

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?

A single dense paragraph that front-loads the scope and then enumerates the three input modes before closing with the price. Every sentence carries essential information; no filler.

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

Completeness4/5

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

For a simple 3-parameter utility with no output schema and no annotations, the description covers the key behaviors: holiday scope, output semantics per mode, and pricing. It falls short of fully specifying the return structure and edge cases, but is adequate for correct invocation.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by clarifying that end is exclusive and by describing the return for each parameter combination, which the schema does not provide.

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?

Identifies the resource (Brazilian business days) and explains exactly what is returned for each parameter combination, making its function clear. Lacks an explicit verb at the start, but the mode descriptions leave no ambiguity about what the tool computes.

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

Usage Guidelines4/5

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

Provides clear context for each input mode: 'With only date', 'With add', 'With end'. This tells an agent how to invoke the tool for the desired result. No alternative date tools exist among siblings, so no when-not-to-use guidance is needed.

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

All BR Intelligence 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?