Skip to main content
Glama
Sign In
my-mcp-server

my-mcp-server

by Gwyn-Ahchoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

calculate

Compute arithmetic results for two numbers with operator choice (+, -, *, /).

Instructions

두 숫자와 연산자를 입력하면 사칙연산 결과를 반환합니다.

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": {
      "operator": "<operator>",
      "a": "<a>",
      "b": "<b>"
    },
    "name": "calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
operatorYes연산자 (+, -, *, /)
aYes첫 번째 숫자
bYes두 번째 숫자

Output Schema

NameRequiredDescriptionDefault
contentYes계산 결과

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided. Description covers main behavior but does not mention edge cases like division by zero, overflow, or rounding.

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?

Single sentence, no redundancy, front-loaded with key information.

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 simple tool with full schema and output schema, description is adequate. Could improve by noting error handling or return format.

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 coverage is 100% with clear parameter descriptions. The description adds no additional meaning beyond 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?

Description clearly states it performs basic arithmetic with two numbers and an operator, using specific verb+resource. Sibling tools are unrelated, so no confusion.

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 guidance on when or when not to use. While the tool is simple, the description omits any context about alternatives or prerequisites.

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

Deploy Server

Other Tools