Skip to main content
Glama
Arnie936

MCP All-in-One Server

by Arnie936
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

subtract

Calculate the difference by subtracting the second number from the first.

Instructions

Subtract b from a

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • calculator_server/server.py:186-189 (handler)
    The subtract tool handler function. Registered with @mcp.tool() decorator, takes two floats (a, b) and returns a - b.
    @mcp.tool()
def subtract(a: float, b: float) -> float:
    """Subtract b from a"""
    return a - b
  • calculator_server/server.py:186-186 (registration)
    The @mcp.tool() decorator on line 186 registers the subtract function as an MCP tool.
    @mcp.tool()

Tool Definition Quality

A3.5/5.0
Behavior2/5

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

With no annotations, the description must convey behavioral traits. It only states the basic operation, omitting details like return value type, error handling, or edge cases. The presence of an output schema is not leveraged in the description.

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 description is a single, front-loaded sentence with no wasted words. It conveys the core functionality efficiently.

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?

Given the tool's simplicity and the presence of an output schema, the description adequately defines the purpose. However, for a tool with no annotations, a bit more context on return or behavior would improve completeness.

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 description does not add parameter-specific meaning beyond the names and types. It confirms order but fails to provide constraints or additional context that would compensate for the lack of schema descriptions.

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 'Subtract b from a' is a specific verb+resource statement that clearly defines the operation and order. It distinguishes the tool from siblings like add, divide, and multiply.

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?

No explicit usage guidelines are provided, but for a simple arithmetic tool, the context of use is implied. However, there is no comparison to alternatives or when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Arnie936/Agentic-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server