Skip to main content
Glama
LostInBrittany

RAGmonsters Custom PostgreSQL MCP Server

add

Calculate the sum of two numbers using a straightforward API endpoint on the RAGmonsters Custom PostgreSQL MCP Server.

Instructions

Add two numbers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

Implementation Reference

  • Registration of the 'add' tool including schema and inline handler function
    server.addTool({
      name: "add",
      description: "Add two numbers",
      parameters: z.object({
        a: z.number(),
        b: z.number(),
      }),
      execute: async (args) => {
        return String(args.a + args.b);
      },
    });
  • The handler function that executes the addition of two numbers and returns the result as a string
    execute: async (args) => {
      return String(args.a + args.b);
    },
  • Input schema using Zod defining two required number parameters 'a' and 'b'
    parameters: z.object({
      a: z.number(),
      b: z.number(),
    }),
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Add' implies a simple mathematical operation, it doesn't address potential behavioral traits such as error handling (e.g., overflow), performance characteristics, or any side effects. The description is minimal and lacks necessary context for safe invocation.

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 'Add two numbers' is extremely concise—a single three-word phrase—with zero wasted words. It's front-loaded and directly communicates the core function without any unnecessary elaboration, making it efficient for quick comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (two numeric parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the return value (e.g., sum of the numbers), error conditions, or any behavioral nuances. For even a basic tool, more context is needed to ensure reliable agent operation.

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?

The input schema has 0% description coverage, so parameters 'a' and 'b' are undocumented in structured fields. The description 'Add two numbers' implies these parameters are numbers to be added, adding some semantic meaning beyond the schema's type constraints. However, it doesn't specify details like acceptable ranges or units, leaving gaps in parameter understanding.

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 'Add two numbers' clearly states the tool's function with a specific verb ('Add') and resource ('two numbers'), making the purpose immediately understandable. However, it doesn't distinguish this tool from potential sibling tools (like 'multiply' or 'subtract'), which would require explicit differentiation for a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or exclusions, leaving the agent with no information about appropriate usage scenarios beyond the basic function stated.

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

Related Tools

  • @zhangzhefang-github/mcp-add-server
  • @kylekanouse/Test-MCP---DEMO-MCP-Dev-1
  • @Mtar786/mcpServer
  • @wrtnlabs/calculator-mcp
  • @YuheiNakasaka/arithmetic-mcp-server
  • @epicweb-dev/epic-me-mcp

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/LostInBrittany/RAGmonsters-mcp-pg'

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