Skip to main content
Glama

Bézout coefficients

bpj_discrete_bezout
Read-onlyIdempotent

Find the greatest common divisor and integer coefficients satisfying Ax + By = gcd(A,B).

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

Input Schema

NameRequiredDescriptionDefault
aYes
bYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so safety is covered. The description does add value by stating what is returned (the gcd plus the two coefficients), which matters because there is no output schema. It says nothing about sign conventions for the coefficients, uniqueness, or edge cases.

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 sentence that front-loads the operation and encodes the result relationship compactly, with no filler.

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-integer, pure-computation tool with full annotation coverage, this is nearly complete: the operation and its outputs are stated. The remaining gaps are minor edge-case details (coefficient sign, gcd of 1) rather than anything blocking a correct call.

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 0%, so the description must carry the load, and it does map A and B into the equation (A pairs with the first coefficient, B with the second), implying order significance. It does not restate or explain the positivity and upper-bound constraints that the schema encodes via minimum/maximum.

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 names a specific verb ('Find') and two concrete outputs (gcd and Bézout coefficients) and pins them down with the equation Ax + By = gcd(A,B), which makes the operation unambiguous. It does not explicitly contrast with nearby siblings such as modular_inverse or congruence_pair, so it stops short of full sibling differentiation.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. An agent must infer from the math alone that this is the tool for Diophantine/Bézout problems rather than, say, modular_inverse.

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.