Skip to main content
Glama

Pirate Weather

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

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

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations indicate idempotentHint=true and destructiveHint=false. Description adds important context about persistence (authenticated vs anonymous, 24-hour retention) and that data is scoped by identifier, going beyond 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 with no filler. Each sentence conveys essential information: purpose, usage timing, and behavioral details.

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 covers what the tool does, when to use, and how the data is stored. No gaps given the tool's simplicity.

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?

Input schema has 100% coverage with clear descriptions for both key and value. Description includes example values but adds limited extra meaning beyond the schema, meeting the baseline.

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 'Save data the agent will need to reuse later' and provides examples (resolved ticker, target address, user preference). It distinguishes itself from sibling tools like recall and forget by explicitly mentioning them.

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?

Explicitly says 'Use when you discover something worth carrying forward' and advises to pair with recall and forget. Also clarifies authentication scope and retention duration.

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