push_contempt_mcp

by ness1-contempt

Overview Schema Source Related Servers Discussions Admin

Python

Local

somma

Adds two numbers together and returns their sum. Use it for quick arithmetic in calculations or data checks.

Instructions

Somma due numeri.

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": "somma"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, and it discloses almost nothing: no mention of precision, rounding, handling of very large numbers, or what the sum is returned as. The existence of an output schema covers the return shape, but the behavioral profile of a pure computation tool is otherwise undocumented.

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 zero waste and the operation front-loaded. It is efficient, though the brevity shades into under-specification rather than disciplined conciseness.

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 an agent can call it correctly without much prose. Still, with no annotations and 0% parameter coverage, the description could have cheaply confirmed operand meaning and numeric behavior; it stops at the minimum.

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% — the parameters are bare 'A' and 'B' with only a numeric type. The phrase 'due numeri' implies both parameters are the addends, which is a small amount of meaning, but it does not say which is which (harmless for addition) or what units/precision are expected.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the operation (addition) and the operand count (two), which is enough for an agent to know what the tool does. However, 'Somma due numeri' largely restates the tool name 'somma' and adds no differentiation from siblings — though none of the listed siblings perform arithmetic, so differentiation is less critical here.

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 guidance on when to use this tool, when not to, or what alternatives exist. Given the surrounding catalogue of e-commerce/SEO tools, even a note that this is a generic arithmetic utility unrelated to the catalogue workflow would help the agent place it.

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