Brawler MCP Server (Python)

Add

add

Sums two integers and returns the result as structured output for calculations that require integer totals.

Instructions

Add two integers and return structured output.

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "add"
  }
}

Input Schema

Name	Required	Description	Default
`a`	Yes
`b`	Yes

Output Schema

Name	Required	Description	Default
`sum`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 26, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that output is structured, which is the main behavioral fact, but says nothing about boundary behavior for large values, overflow, or negative inputs — reasonable gaps for a pure function, but gaps nonetheless.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no padding. The trailing 'and return structured output' is mildly redundant given an output schema exists, but it is not wasteful.

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?

The tool is trivial and an output schema exists, so return values need not be explained. However, with no annotations and zero schema description coverage, the description leaves the parameter roles and any behavioral limits undocumented, which is the minimum-viable bar rather than a complete one.

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 0% and the parameters are named only 'a' and 'b'. The description says 'two integers', which weakly confirms both operands are integers, but adds no mapping of which param is which operand nor any constraint information (they are required, additionalProperties false). With low coverage the description should have compensated and does not.

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?

States a specific verb and resource: add two integers. That is unambiguous against siblings like echo, ping, or route, though the description makes no explicit effort at sibling differentiation. The purpose is clear without opening the schema.

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?

Usage is only implied — an agent infers this is the arithmetic tool, but there is no statement of when to use it, when not to, or which sibling to prefer. For a primitive like this, a brief scoping note would still help.

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

Deploy Server

Add