Skip to main content
Glama

Noaa Spc

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.3/5.0
Behavior4/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds valuable behavioral context: scoped by identifier, persistent for authenticated users, 24-hour retention for anonymous sessions. No contradiction with 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 three sentences, each serving a distinct purpose: purpose, usage guidance, persistence details. It is front-loaded with the core action and avoids fluff.

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?

For a simple 2-parameter write tool with no output schema, the description fully covers purpose, usage, persistence, and sibling pairing (recall, forget). It leaves no significant gaps.

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 coverage is 100%, so baseline is 3. The description provides example values for key (e.g., 'subject_property') and clarifies value can be any text, adding modest extra meaning beyond the schema descriptions.

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

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 gives clear guidance on when to use: 'Use when you discover something worth carrying forward.' It also notes persistence differences for authenticated vs. anonymous users, but does not explicitly state when not to use or provide alternatives.

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

All Noaa Spc 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.4/5.0
Disambiguation1/5

Several tools overlap heavily: ask_pipeworx and ask_pipeworx_beta are currently identical, and there are six polymarket_* tools plus bet_research for the same prediction-market domain. AI visibility and company profile tools also overlap, making selection genuinely ambiguous.

Naming Consistency3/5

All names are lowercase snake_case, which is consistent formatting, but the pattern is mixed: some are verb_noun (ask_pipeworx, generate_llms_txt, validate_claim) while many are noun-first (convective_outlook, polymarket_edges, entity_profile) or adjective-noun (recent_alerts, watches_active). It's readable but not a uniform verb_noun convention.

Tool Count2/5

35 tools is above the 25-tool threshold, and more importantly the set is bloated with a general-purpose research platform when the server is named Noaa Spc. Only 4 tools actually serve the SPC domain, so the count is inappropriate for the stated purpose.

Completeness3/5

For the dominant Pipeworx domain, the surface is fairly broad (query, compare, validate, subscribe, remember), but there are notable gaps: no update for subscriptions, no generic weather beyond SPC, and no direct list of all available sources. For the SPC purpose implied by the name, only 4 of 35 tools exist, so coverage is severely skewed.

Resources