Skip to main content
Glama
mcp-airlock

mcp-airlock

by sigma5667

Get Sum Tool

get-sum
Read-onlyIdempotent

Calculates the sum of two numbers and returns the total for arithmetic use in mcp-airlock workflows.

Instructions

Returns the sum of two numbers

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": "get-sum"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesFirst number
bYesSecond number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety and purity profile is fully covered without the description. The description adds nothing beyond that: no note on numeric range, precision, integer vs float handling, or error behavior for invalid inputs.

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?

A single short sentence with the operation front-loaded and no filler. It is appropriately sized for a trivial tool, though it is too terse to be considered exemplary.

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 two-parameter arithmetic helper with full schema coverage and complete annotations, the description supplies everything needed to call it correctly. No output schema exists, but the return value is self-evident from 'Returns the sum'.

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 description coverage is 100% ('First number' / 'Second number'), so the schema does the parameter documentation work. The description only restates that two numbers are involved and adds no meaning such as ordering, precision, or accepted formats, so the baseline of 3 applies.

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 names a specific operation and resource: it returns the sum of two numbers, which is exactly what an agent needs to distinguish a pure arithmetic helper from the surrounding demo tools (env, header, resource, trigger tools). It does not explicitly differentiate itself from siblings by name, but the semantics are unambiguous.

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?

There is no when-to-use guidance, no statement of constraints on inputs, and no mention of alternatives. An agent must infer that this is a generic arithmetic utility purely from the verb 'Returns the sum'.

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