Skip to main content
Glama

Press Release

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

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

Annotations indicate idempotent and non-destructive. Description adds context about session-based persistence: 'authenticated users get persistent memory; anonymous sessions retain memory for 24 hours'. No contradictions.

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 four sentences, each well-formed and informative. It front-loads the purpose, then provides usage context and storage details without unnecessary words.

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 key-value store with complete parameter schema, the description covers essential aspects: what to store, scope, duration, and links to related tools. Could mention overwrite behavior for existing keys, but not critical.

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 descriptions for both parameters. The tool description adds value by providing concrete examples of key names and value types, aiding the agent in proper usage.

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 verb 'save data' and the resource 'data the agent will need to reuse later'. It includes specific examples like 'resolved ticker', 'target address', 'user preference', and distinguishes from siblings '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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use: 'when you discover something worth carrying forward'. It also mentions complementary tools: 'pair with recall to retrieve later, forget to delete', providing clear guidance on alternatives.

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

All Press Release 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.8/5.0
Disambiguation2/5

Several tools have unclear boundaries: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical variants (beta is explicitly identical to stable), and the six Polymarket tools heavily overlap in finding edges and arbitrage. discover_tools and suggest_questions also serve similar discovery purposes, causing likely misselection.

Naming Consistency4/5

All names are lowercase snake_case with mostly verb-first or clear prefixes (ask_, polymarket_, pipeworx_, recent_). Minor deviations like `press_release_generate` (noun-verb) and `entity_profile` (noun-noun) break the otherwise consistent pattern, but the naming remains readable and predictable.

Tool Count2/5

At 32 tools, the count exceeds the 25+ threshold and feels bloated for a server whose stated purpose is 'Press Release.' The toolset sprawls across unrelated domains (data lookups, prediction markets, memory, AI visibility, npm scanning), making the size more of a liability than a well-scoped strength.

Completeness2/5

For a server named 'Press Release,' the surface is severely incomplete: only one satirical press release generator exists, with no drafting, editing, publishing, or distribution tools. The other 31 tools serve unrelated domains, so an agent expecting press-release lifecycle support hits significant dead ends.

Resources