Skip to main content
Glama

sunrisesunset

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. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "key": "user_research_topic"
+  },
+  {}
+]
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is clear. The description adds valuable behavioral context by explaining the identifier scoping (anonymous IP, BYO key hash, or account ID) and the list-all-keys behavior when the key is omitted, 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?

The description is concise and front-loaded with the core action. Each sentence adds value: the retrieval/list action, usage context, scoping detail, and pairing with sibling tools. There is no redundancy or filler.

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?

The description covers the main functionality, optional behavior, scoping, and related tools. Since there is no output schema, it implies the return value (the stored value or list of keys) without spelling out format, which is sufficient for this simple tool.

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 description coverage is 100% for the single 'key' parameter, with the schema already explaining 'omit to list all keys'. The description repeats this behavior without adding additional parameter-level details, so it does not meaningfully augment the schema.

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 uses specific verbs ('retrieve', 'list') and a specific resource (saved memory), and it distinguishes the tool from siblings by explicitly naming the paired tools 'remember' and 'forget'. It also clarifies the optional key behavior, making the purpose unmistakable.

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?

The description explicitly states when to use the tool ('Use to look up context the agent stored earlier') and gives concrete examples. It also mentions the pairing with 'remember' to save and 'forget' to delete, effectively covering alternatives and context.

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

All sunrisesunset 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.7/5.0
Disambiguation4/5

Most tools have distinct purposes with detailed descriptions, but there is overlap among closely related Polymarket tools (e.g., bet_research, polymarket_edges, polymarket_arbitrage) and between ask_pipeworx and ask_pipeworx_grounded, which could cause misselection.

Naming Consistency3/5

Tool names mix verb_noun, noun_verb, and descriptive phrases inconsistently (e.g., get_times vs listen_subscriptions vs bet_research), and while many use underscores, conventions vary, making patterns hard to predict.

Tool Count3/5

With 32 tools, the server feels overloaded, covering distinct domains (sunrise, Pipeworx, Polymarket, memory, subscriptions) under one name, making it a 'Swiss army knife' rather than a focused toolset.

Completeness2/5

The server name suggests a narrow domain (sunrise/sunset) but only 2 of 32 tools address it, ignoring related weather data. While other domains are covered, operations lack depth (e.g., no subscription updates, no memory search).

Resources