mcp-research-collective

by SiegKat

Overview Schema Related Servers Score Discussions

Local

subtract

Calculate the difference by subtracting b from a, returning the result.

Instructions

Subtract b from a.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Implementation Reference

src/mcp_research_collective/mcp_server.py:86-88 (handler)
The subtract tool handler: decorated with @mcp.tool(), takes two floats a and b, returns a - b.
```
def subtract(a: float, b: float) -> float:
    """Subtract b from a."""
    return a - b
```
src/mcp_research_collective/mcp_server.py:85-85 (registration)
The @mcp.tool() decorator on line 85 registers subtract as an MCP tool on the FastMCP server instance.
```
@mcp.tool()
```

Tool Definition Quality

B3.4/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 full burden. It lacks details on number types, precision, overflow, or result handling, which are important for behavioral expectations.

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 sentence with no unnecessary words. It is efficiently structured and front-loaded with the essential operation.

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?

For a simple arithmetic operation, the description suffices, but it could be more complete by mentioning output format or handling edge cases, especially since an output schema exists.

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?

The description clarifies the roles of parameters a and b (a is the minuend, b is the subtrahend), but with 0% schema coverage, it does not compensate fully for the lack of parameter descriptions in the schema.

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' clearly specifies the verb (subtract) and the resource (two numbers), distinguishing it from sibling tools like add, multiply, and divide.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives, but the purpose is implicitly understood from the tool name and statement. No exclusions or conditions are mentioned.

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

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

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/SiegKat/mcp-agent-blackboard'

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