Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

math_fibonacci_generator

Read-onlyIdempotent

Generate Fibonacci sequences, compute the nth term, test if a number is a Fibonacci number, or list Fibonacci values in a range. Exact BigInt results.

Instructions

Fibonacci Sequence Generator. Generate a Fibonacci sequence, compute the nth term via fast doubling, test whether a number is a Fibonacci number, or list every Fibonacci value in a range. The output is fully DETERMINISTIC (same input always yields the same result) and exact via BigInt, with values returned as decimal strings; supports indices up to F(50000) and range bounds up to 10 to the power 200. Use math_prime_number_checker for primality, or math_factorial_calculator for factorials and combinations. Runs locally as pure computation: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/minute for anonymous callers). Returns a result object whose shape depends on the chosen operation (a values array, an nth value, a membership flag, or a range listing).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesWhich computation to run. sequence lists count terms from start; nth returns the single nth term; isFibonacci tests membership of n; range lists Fibs between from and to.
countNoNumber of terms to emit (operation sequence only). Required for sequence; must be 1 to 2000.
startNoZero-based index of the first term emitted (operation sequence only). Optional; defaults to 0; must be 0 to 50000.
nNoIndex for operation nth (0 to 50000), or the value to test for operation isFibonacci (non-negative; very large values may be passed as a numeric string). Required for nth and isFibonacci.
fromNoInclusive lower value bound (operation range only). Required for range; non-negative and not greater than to.
toNoInclusive upper value bound (operation range only). Required for range; non-negative and at most 10 to the power 200.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the computation succeeded.
resultNoOperation-specific payload. Fields below are the union across all operations; only the fields for the chosen operation are present.
errorNoError message when success is false (HTTP 400).
Behavior5/5

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

Beyond annotations (readOnlyHint=true, idempotentHint=true), description adds deterministic behavior, BigInt exactness, decimal string output, index/range bounds, rate limit, and return value shape variability. 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?

Single paragraph with effective front-loading of main operations. Every sentence contributes value. Could be slightly more structured (e.g., bullet points) but remains clear and concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's multiple operations, 6 parameters, and output schema existence, the description covers all necessary context: operation types, constraints, limits, behavior, rate limiting, and return value variability.

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 100%, so description's added value is limited. It provides high-level context (e.g., operation types) but does not significantly enrich individual parameter understanding beyond the schema's own descriptions.

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 clearly states the tool generates Fibonacci sequences, computes nth term via fast doubling, tests membership, and lists values in a range. It distinguishes itself from siblings by naming alternatives (math_prime_number_checker, math_factorial_calculator).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use this tool (for Fibonacci operations) and when to use alternatives (primality, factorials). Also provides context: runs locally, read-only, non-destructive, no external service, rate-limited.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server