Skip to main content
Glama

Fast-doubling Fibonacci number

bpj_discrete_fibonacci
Read-onlyIdempotent

Compute an exact Fibonacci term by fast doubling with F0 = 0 and F1 = 1.

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": {
      "index": "<index>"
    },
    "name": "bpj_discrete_fibonacci"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already state read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful behavioral context beyond that: it guarantees an exact result and defines the indexing convention with F0=0 and F1=1. It does not state the return type explicitly, but for a simple Fibonacci calculation this is a minor gap.

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?

The description is a single front-loaded sentence with no wasted words. Every clause adds useful information: exactness, algorithm, and base cases.

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 low-complexity, single-parameter mathematical tool with annotations covering safety, this is nearly complete. The description explains the computation and seed convention; the only minor omission is an explicit statement of the return type, though 'exact Fibonacci term' strongly implies an integer.

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 description coverage is 0%, so the description must carry parameter meaning. It does so by defining the Fibonacci seed values F0=0 and F1=1, which clarifies how the required 'index' parameter maps to terms. The upper bound of 2000 is left to the schema, which is acceptable.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: 'Compute an exact Fibonacci term'. It further specifies the method ('by fast doubling') and the seed convention ('F0 = 0 and F1 = 1'), making the tool's purpose unmistakable and distinguishable from unrelated discrete-math siblings.

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 clear purpose: use this to compute a Fibonacci term. However, the description gives no explicit when-to-use guidance, no exclusions, and no comparison to alternatives. The seed convention helps, but there is no stated context for choosing this over other calculation approaches.

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.