Skip to main content
Glama

gcd_lcm_calc

Read-onlyIdempotent

Calculate the greatest common divisor and least common multiple for two or more integers by entering values or a comma-separated list.

Instructions

Calculate GCD and LCM 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": "gcd_lcm_calc"
  }
}

Input Schema

NameRequiredDescriptionDefault
aNoFirst integer.
bNoSecond integer.
numbersNoComma-separated integers (or use a and b).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered externally. The description adds no behavioral context such as how the two input forms interact, whether both GCD and LCM are returned, or edge-case handling (negatives, zero).

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?

A single front-loaded sentence with no filler; the verb and resource lead immediately.

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?

There is no output schema, and the description never says whether the result contains both GCD and LCM or how they are keyed. For a mathematical tool that computes two quantities, that return-value ambiguity is a meaningful gap even though the input side is fully covered.

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% and the schema itself labels a, b, and the comma-separated numbers string, so the baseline is 3. The description only restates the input type ('integers') and adds no guidance on precedence when both a/b and numbers are supplied.

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?

States a specific verb ('Calculate') and resource ('GCD and LCM'), and clarifies the input scope ('two or more integers'). It does not explicitly differentiate itself from the sibling gcd_calculate or extended_gcd, so an agent must infer the difference from the name alone.

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?

Usage is only implied by the nature of a pure math utility; there is no statement of when to prefer this over gcd_calculate or lcm-related siblings, nor any note that a and b are alternatives to the numbers string.

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