Skip to main content
Glama

Least common multiple of a list

bpj_discrete_lcm_list
Read-onlyIdempotent

Reduce a list of positive integers to its exact least common multiple.

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": {
      "values": "<values>"
    },
    "name": "bpj_discrete_lcm_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so safety is covered. The description adds the domain restriction to positive integers and the promise of an exact (not approximate/floating) result, which is marginally useful, but says nothing about ordering, duplicates, empty-list handling, or size limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler. It is terse rather than padded, though the terseness contributes to the missing input-format detail.

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?

For a single-parameter pure function this is close to adequate, and no output schema exists so the description reasonably signals the return value. However, the ambiguous string-vs-array input format and edge cases (empty list, single element) are left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and there is a single parameter whose actual wire format is unusual — a string field containing a JSON array, capped at 1500 characters. The description only says 'list of positive integers' and never clarifies the string-encoded JSON array requirement or the length cap, so it fails to compensate for the coverage gap.

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?

Specific verb ('reduce') and resource ('list of positive integers') with a named result ('exact least common multiple'). Clearly separable from sibling discrete-math tools such as bezout, prime_factors, or gcd-style helpers, though it does not explicitly name an alternative.

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?

No when-to-use or when-not-to-use guidance; the agent must infer that this is the aggregation tool for multiple values. No mention of how it relates to prime factorization or to single-pair LCM operations.

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.