Skip to main content
Glama

Pirate Weather

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. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint, idempotentHint, and destructiveHint false. Description adds scoping detail (by identifier) and pairing info, complementing annotations without contradiction.

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?

Two sentences, front-loaded with purpose, no redundant words. Efficient and clear.

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?

Without output schema, description explains return values (value or list of keys) and scoping. While sufficient, it could briefly mention response format (e.g., JSON structure) for completeness.

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 description for the key parameter. Tool description adds value by explaining behavior when key is omitted (list all keys), which is not explicit in schema alone.

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?

Description clearly states verb ('retrieve' or 'list') and resource ('saved values/keys'), and distinguishes from siblings 'remember' and 'forget'. Includes examples for both cases.

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?

Provides explicit context: 'look up context the agent stored earlier' and mentions pairing with remember/forget. However, lacks explicit when-not-to-use or comparison to other sibling tools like search.

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

All Pirate Weather 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

B3.1/5.0
Disambiguation3/5

Tools are mostly distinct in purpose but some overlaps exist, e.g., multiple ask_pipeworx variants and several polymarket analysis tools. Detailed descriptions help, but the sheer variety and similar intent of some tools could confuse agents.

Naming Consistency2/5

Naming is highly inconsistent: snake_case (ai_visibility_check), single words (forecast), action_noun (bet_research), prefixes (polymarket_, pipeworx_), and descriptive phrases (scan_competitor_ai_presence). No uniform pattern.

Tool Count2/5

33 tools is too many for a server named 'Pirate Weather' that only has two weather-specific tools. The tool count feels inflated with many meta-tools and unrelated domains, exceeding a coherent scope.

Completeness2/5

Coverage is incomplete for the implied weather focus (only two tools). Other domains like prediction markets are better covered, but overall the surface is a mix of partial offerings with clear gaps (e.g., no update/delete for subscriptions).

Resources