Skip to main content
Glama

Euler totient

bpj_discrete_euler_totient
Read-onlyIdempotent

Count positive integers up to n that are coprime to n using its distinct prime factors.

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>"
    },
    "name": "bpj_discrete_euler_totient"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYes

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 establish read-only, idempotent, non-destructive, closed-world behavior, so the description need only add domain context. It gives the mathematical definition and notes reliance on distinct prime factors, but does not disclose output type, edge-case behavior for n=1, or handling of the schema's maximum value. No contradiction with annotations.

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?

A single front-loaded sentence with no filler. The only inefficiency is the mismatch between the described 'n' and the schema's 'a', and the implementation detail about distinct prime factors is secondary.

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 simple one-parameter read-only math tool with annotations covering safety, the description conveys enough to understand the computation. However, the parameter naming mismatch and absence of return-type or edge-case clarification leave gaps for reliable invocation.

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%, so the description should compensate by explaining the sole parameter. Instead it refers to 'n' while the schema parameter is named 'a', and it adds no explicit range or constraint meaning beyond the schema's minimum and 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?

States a specific verb and mathematical resource: counting positive integers up to n coprime to n, which is exactly the Euler totient function. The purpose is clear, though no sibling tool is named or explicitly distinguished.

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?

Provides no guidance on when to use this tool versus alternatives such as prime_factors or prime_sieve. There are no exclusions, prerequisites, or usage conditions; the agent must infer usage from the mathematical definition alone.

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.