Skip to main content
Glama

Math.Tools MCP Server

Gcf Lcm Tool

gcf-lcm

Compute the greatest common factor (GCF/GCD) or least common multiple (LCM) of two or more numbers. Requires a math.tools API token (numbers:* ability).

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": {
      "op": "<op>",
      "numbers": "<numbers>"
    },
    "name": "gcf-lcm"
  }
}

Input Schema

NameRequiredDescriptionDefault
opYesWhich operation to perform.
numbersYesComma-separated list of integers, e.g. '12,18,24'. At least two values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose one important behavioral fact: a math.tools API token with the numbers:* ability is required. It says nothing about rate limits, error behavior, or what the result looks like (presumably a single integer), leaving meaningful gaps.

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?

Two short sentences: the operation and scope come first, the prerequisite second. Every clause earns its place, including the GCF/GCD alias that clarifies the abbreviation.

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 two-parameter, fully-described-schema tool with no output schema, the definition covers what the tool does and what credential it needs. The only real omission is the shape of the result, which is minor for a simple arithmetic utility.

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 both the enum 'op' and the comma-separated 'numbers' string are already well documented. The description only reinforces the 'two or more numbers' minimum, adding little beyond the schema, so baseline 3 applies.

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 gives a specific verb (compute) and precise resources (greatest common factor / least common multiple), and resolves the cryptic tool name 'gcf-lcm' by noting the GCF/GCD alias. It does not explicitly differentiate from siblings such as number-theory-check, but the operation is unambiguous.

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 implied clearly enough that an agent knows this is the tool for GCD/LCM computations, but there is no explicit when-to-use versus when-not guidance and no mention of alternatives. Prerequisites (the API token) are stated, which is a partial substitute.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources