Skip to main content
Glama
Sign In

Scientific Calculator

by ai.saifs
OverviewDiscussionsAdmin

GCD / HCF Calculator

calculator_gcd
Read-only

Greatest Common Divisor (GCD/HCF) of two or more integers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calculator_gcd"
  }
}

Input Schema

NameRequiredDescriptionDefault
aNoFirst integer (alt).
bNoSecond integer (alt).
numbersNoIntegers.

Output Schema

NameRequiredDescriptionDefault
gcdYes
resultYes
numbersYes
expressionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds that it works on 'two or more integers,' but does not disclose behavior for zero, negative numbers, or invalid/empty input, so it adds little beyond the safety annotations.

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 text. For a simple calculator operation, this is appropriately sized.

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 simple operation, full schema description coverage, rich read-only annotations, and an output schema, the description is largely sufficient. The only notable gap is edge-case behavior for zero or negative inputs.

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 description coverage is 100%, so the schema already documents a, b, and numbers. The description's phrase 'two or more integers' is consistent with the variadic numbers input but does not clarify the alternate a/b vs. numbers relationship beyond what the schema provides.

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 states a specific mathematical operation and resource: GCD/HCF of integers. It is clear enough to distinguish this from most calculator siblings, but it does not explicitly contrast with closely related tools such as calculator_lcm or calculator_factor.

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?

It gives no explicit when-to-use guidance, no exclusions, and no alternatives. An agent can infer that this computes GCD, but nothing tells it when to choose this over calculator_lcm or calculator_factor.

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

All Scientific Calculator toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources