Skip to main content
Glama

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. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations indicate idempotent and non-destructive, but the description adds meaningful behavior: key-value storage, scoping by identifier, persistence differences between authenticated and anonymous sessions, and 24-hour retention for anonymous. This goes beyond annotations without contradicting them.

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, all substantive and front-loaded. Every sentence adds a distinct piece of information: purpose, usage criteria, and behavioral details, with no filler or redundancy.

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 two-parameter memory tool with no output schema, the description covers storage semantics, persistence, scoping, and companion tools. It doesn't mention overwriting behavior for existing keys, but the idempotent hint partially covers that, and overall this is quite complete.

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 covers 100% of the two parameters with clear descriptions, so baseline 3 is appropriate. The description adds general context about key-value storage but no extra parameter-level detail beyond what the schema already provides.

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?

Uses a specific verb 'Save' with a clear resource ('data the agent will need to reuse later'), and distinguishes itself from siblings by explicitly mentioning 'recall' and 'forget' as companion tools. The scope ('across this conversation or across sessions') adds further clarity.

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 states when to use ('Use when you discover something worth carrying forward') and gives concrete examples. It also specifies actions to avoid redundancy by pairing with recall/forget, giving clear context and alternatives.

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

All 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

A3.6/5.0
Disambiguation2/5

Several tools have overlapping purposes, particularly the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) where the beta variant is currently identical to the stable one, creating selection ambiguity. Additionally, many data-lookup tools (entity_profile, compare_entities, recent_changes, validate_claim) could be confused for similar queries, and the three weather tools are buried among unrelated prediction-market and utility tools.

Naming Consistency2/5

Tool names are all snake_case, but the pattern is inconsistent: some are verb-first (get_forecast, list_subscriptions, remember), while others are noun-first or noun phrases (polymarket_edges, pipeworx_trending, entity_profile, bet_research). The mix of verbs and nouns without a clear convention makes the interface feel unstructured.

Tool Count1/5

With 34 tools, the count is far too high for a server nominally focused on weather, which only has 3 relevant tools. The majority of tools are unrelated to weather (Pipeworx data, prediction markets, memory, subscriptions), making the scope seem bloated and misaligned with the server name.

Completeness3/5

For the weather domain itself, the coverage is adequate (real-time, forecast, historical), but the server includes many unrelated tools that create confusion about its true purpose. The extra tools neither enhance weather functionality nor form a coherent secondary domain, leaving the overall surface feeling incomplete for a single coherent use case.

Resources