Skip to main content
Glama
Sign In

Oeis

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Sequence

get_sequence
Read-onlyIdempotent

Fetch a single OEIS integer sequence by its A-number (e.g. "A000045" for the Fibonacci numbers, "A000040" for the primes). Accepts the A-number with or without the "A" prefix and zero-padding ("A000045", "45", and "000045" are all valid). Returns the full record: name, terms (data), comments, formulas, keywords, offset, author, and reference count. Use this to get the formula or mathematical description of a known sequence.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "A000045"
    },
    "name": "get_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn OEIS A-number such as "A000045", or just "45" / "000045".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "A000045"
+  },
+  {
+    "id": "45"
+  }
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, aligning with the description's 'Fetch' operation. The description adds value by detailing input flexibility (prefix, zero-padding) and listing returned fields (name, terms, comments, formulas, etc.). No contradictions.

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?

Three sentences with the main purpose first, followed by input examples and output details, ending with a usage hint. Every sentence is informative, no waste. Highly efficient.

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?

Given no output schema, the description lists seven return fields (name, terms, data, comments, formulas, keywords, offset, author, reference count), covering expected results. It doesn't specify data types or structure, but for a simple fetch tool, this is sufficient and complete enough.

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?

The schema covers the single parameter 'id' with 100% coverage, including examples. The description complements this by providing concrete examples (e.g., A000045, A000040) and clarifying valid input formats. This adds meaning but doesn't drastically exceed the schema's baseline.

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 fetches a single OEIS integer sequence by its A-number. The verb 'fetch' and resource 'OEIS integer sequence' are specific. It also distinguishes from the sibling 'search_sequence' by focusing on retrieval by exact ID.

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

Usage Guidelines4/5

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

The description advises using this tool to 'get the formula or mathematical description of a known sequence,' implying it is for when the A-number is known. It does not explicitly state when not to use it, but the sibling 'search_sequence' is implied for lookup by name or description. Adequate guidance.

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

All Oeis toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources