Skip to main content
Glama
Sign In

Oeis

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Sequence

search_sequence
Read-onlyIdempotent

Search the OEIS (On-Line Encyclopedia of Integer Sequences), the authoritative database of integer sequences. Identify a sequence from its first terms by passing a comma-separated list of integers (e.g. "1,1,2,3,5,8" finds the Fibonacci numbers), look up a specific sequence by A-number (e.g. "A000045"), or search free-text keywords (e.g. "prime gaps"). Returns up to 10 matching sequences per page with their A-number, name, terms, keywords, author, and offset. Use the start argument to paginate (10 results at a time).

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": {
      "query": "1,1,2,3,5,8"
    },
    "name": "search_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA comma-separated list of integers (e.g. "1,1,2,3,5,8"), an A-number (e.g. "A000045"), or free-text keywords (e.g. "prime gaps").
startNoPagination offset; results come 10 at a time. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "1,1,2,3,5,8"
+  },
+  {
+    "query": "A000045"
+  },
+  {
+    "query": "prime gaps",
+    "start": 0
+  }
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already indicate readOnly, openWorld, idempotent, and non-destructive. The description adds concrete behavior: returns up to 10 results per page, supports pagination via the 'start' parameter, and lists returned fields (A-number, name, terms, keywords, author, offset). 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?

The description is three sentences, front-loaded with the tool's main purpose, and every sentence adds essential information without redundancy.

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?

Despite no output schema, the description fully explains what the tool returns (up to 10 sequences per page with specific fields) and how pagination works. It covers all necessary context for an agent to use the tool correctly.

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 100%, with schema descriptions for both parameters. The description adds value by providing usage examples and clarifying that the 'query' can be comma-separated integers, an A-number, or free-text, and that 'start' is a pagination offset.

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 it searches the OEIS for integer sequences, and specifies three distinct use cases: identifying a sequence from its terms, looking up by A-number, or free-text keyword search. This contrasts with sibling tools like 'get_sequence', which likely retrieves a single sequence by 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 explicitly explains when to use the tool (for sequence lookup by terms, A-number, or keywords) and mentions pagination. While it does not explicitly state when not to use it or list alternatives, the context from sibling tools like 'get_sequence' provides implicit 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