Skip to main content
Glama

Remoteok

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)

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value by explaining the listing behavior when key is omitted, scoping to identifier, and pairing with related tools, with 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 two sentences, front-loaded with the primary action, and every sentence adds value with no wasted words.

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 simplicity (one optional parameter, no output schema), the description fully covers its purpose, usage, parameter behavior, and scope, making it complete.

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 input schema has 100% coverage for the one optional parameter. The description adds 'omit the key argument to list all keys', providing additional semantics beyond the schema's description.

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 explicitly states 'Retrieve a value previously saved via remember, or list all saved keys', using a specific verb and resource. It clearly distinguishes from sibling tools remember and forget by naming them.

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 provides clear context: 'Use to look up context the agent stored earlier... without re-deriving it from scratch.' It also explains scoping and pairs with remember/forget, though it does not explicitly state when not to use.

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

All Remoteok 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

A3.9/5.0
Disambiguation2/5

Several tool clusters have fuzzy boundaries: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer questions through the same routing layer, while polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, and bet_research all address prediction-market edges. Even with detailed descriptions, an agent can easily select the wrong variant.

Naming Consistency3/5

Names are uniformly lowercase snake_case and many follow a verb_noun pattern (list_jobs, search_jobs, resolve_entity, validate_claim), but there are numerous noun-first and adjective-first exceptions (entity_profile, recent_alerts, pipeworx_trending, polymarket_arbitrage) plus bare verbs (remember, forget, recall, subscribe). The pattern is readable but not consistently applied.

Tool Count2/5

34 tools is well above the well-scoped range, and the vast majority are not about the server's RemoteOK namesake. The set appears to merge several distinct domains (Pipeworx data research, Polymarket betting, RemoteOK jobs, memory utilities) into one oversized surface, making it feel more like a bundled platform than a focused server.

Completeness4/5

For the dominant Pipeworx/data-research theme, coverage is strong: question answering, grounded verification, entity profiles, comparisons, change feeds, discovery, memory, subscriptions, and citation-based research are all present. The RemoteOK job subset covers list/search/get without obvious dead ends. Minor gaps exist (no direct citation-URI fetcher, no job alert subscriptions), but agents can work around them.

Resources