Skip to main content
Glama

Generate a Farey sequence

bpj_discrete_farey_sequence
Read-onlyIdempotent

List all reduced fractions from zero through one with denominators up to a supplied order.

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": {
      "order": "<order>"
    },
    "name": "bpj_discrete_farey_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 behavior, so the safety profile is fully covered structurally. The description adds that the output is a list of reduced fractions restricted to the unit interval, which is useful return-shape context, but it says nothing about ordering of results, output format, or how the sequence grows with order.

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 output and closes with the scoping parameter, with no redundant or filler wording.

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, so the description carries the burden of describing the return value; it conveys the content (reduced fractions in [0,1]) but not the encoding — whether fractions come back as strings like "1/2" or as numerator/denominator pairs. For a one-parameter pure computation tool with complete annotations, that is the main remaining gap.

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

Parameters4/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 parameter's meaning — and it does: "denominators up to a supplied order" disambiguates the bare "Order" title, which would otherwise be opaque. The numeric bounds (1–32) are already in the schema, so the only remaining gap is that the growth/complexity implication of a large order is unstated.

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?

"List all reduced fractions from zero through one with denominators up to a supplied order" gives a specific verb (list) and a precisely bounded mathematical resource, so an agent knows exactly what it gets. It does not distinguish itself from siblings, but the sibling set is a broad catalog of unrelated discrete-math utilities, so no differentiation is genuinely needed.

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 by the definition — you call it when you need the Farey sequence of a given order — and the single-parameter, self-contained nature makes the call obvious. However, there is no statement of prerequisites, no mention of the order cap, and no note about when a different tool might be preferred.

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.