Skip to main content
Glama

Oeis

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value by explaining scoping ('Scoped to your identifier') and pairing with remember/forget, which goes beyond the annotations.

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, each earning its place: first defines action, second gives use cases, third explains scoping and pairing. No redundancy, front-loaded with purpose.

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 simple retrieval tool with no output schema, the description covers input behavior, typical use cases, and scoping. It is complete enough for an agent to use correctly.

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% with a single parameter 'key' described as 'Memory key to retrieve (omit to list all keys)'. The description repeats this essentially but adds context about listing all keys in the first sentence. The addition is marginal.

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 verb ('Retrieve' or 'list'), the resource ('a value previously saved via remember' or 'all saved keys'), and distinguishes from sibling tools (remember, forget). It provides concrete use cases like 'user's target ticker, an address, prior research notes'.

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 states when to use this tool ('Use to look up context the agent stored earlier without re-deriving it from scratch') and mentions scoping. It lacks explicit 'when not to use' or alternatives among the large sibling list, but the context is clear.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools have distinct purposes, but there is some overlap, especially among ask_pipeworx variants (ask_pipeworx, ask_pipeworx_grounded, ask_pipeworx_beta) and prediction market tools (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, bet_research). While descriptions help distinguish them, the boundaries are somewhat fuzzy.

Naming Consistency2/5

Naming conventions are inconsistent. Some tools use verb_noun (search_sequence, compare_entities), others use noun_verb (entity_profile, recent_changes), and some have prefixes (pipeworx_feedback, pipeworx_trending) while others do not (remember, forget). There is no uniform pattern, which reduces predictability.

Tool Count2/5

The server name 'Oeis' suggests a focus on integer sequences, but only 2 of 33 tools are OEIS-related. The remaining tools cover a vast array of unrelated domains (data retrieval, prediction markets, memory, subscriptions). This mismatch between name and scope makes the tool count feel excessive and poorly scoped.

Completeness4/5

Within the broad domains covered, the tool surface is quite complete. For memory, there are remember/recall/forget; for subscriptions, subscribe/unsubscribe/list_subscriptions/recent_alerts; for data retrieval, multiple entry points. Minor gaps exist, such as lack of OEIS sequence contribution tools, but overall the set is well-rounded.

Resources