Skip to main content
Glama

Steam

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)

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds valuable context: key-value scoping, retention periods (24 hours for anonymous), and cross-session persistence. It does not detail overwrite semantics, but the idempotentHint covers that, and the additional context goes beyond the 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, each serving a distinct purpose: stating the core function, providing usage triggers, and explaining storage semantics. No fluff or redundancy, perfectly front-loaded.

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 tool with two parameters and no output schema, the description covers purpose, usage, persistence behavior, authentication differences, and sibling relationships. Nothing essential is missing, making it complete for an agent to select and invoke correctly.

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 examples for both parameters, giving a baseline of 3. The description enriches this with domain-specific examples (ticker, address, preference) and clarifies that the value is arbitrary text, adding meaningful context beyond the schema.

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 uses the specific verb 'Save' and identifies the resource as data for later reuse, clearly distinguishing it from siblings like recall and forget, which are explicitly paired. This is a specific verb+resource statement with clear sibling differentiation.

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?

It provides explicit when-to-use guidance ('when you discover something worth carrying forward') and names companion tools (recall, forget) for retrieval and deletion, making the selection criteria unambiguous. It also notes the persistence difference for authenticated vs. anonymous sessions.

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

All Steam 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

C2.9/5.0
Disambiguation2/5

Many tools overlap significantly: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical variants, while deep_research, discover_tools, and suggest_questions all serve meta/onboarding purposes. The Steam-specific tools are distinct, but they are drowned out by a large unrelated set (Polymarket, Pipeworx, npm scanning) that makes selection confusing.

Naming Consistency2/5

Tool names follow no single convention: some are verb_noun (resolve_vanity_url, generate_llms_txt), some are noun-only (app_details, player_stats), and others use domain prefixes inconsistently (polymarket_arbitrage, ask_pipeworx_grounded, deep_research). The mix of descriptive and vague names (process, run, execute) adds to the inconsistency.

Tool Count2/5

At 45 tools, the server is heavily overloaded, especially for a server named 'Steam' where only about a third of the tools actually relate to Steam. The rest belong to Pipeworx, Polymarket, and other unrelated domains, making the scope unclear and the tool count far too large for a focused purpose.

Completeness3/5

For the Steam domain, the server covers a reasonable range: app details/news, player counts, friends, owned games, achievements, stats, bans, levels, and summaries. However, notable gaps exist such as store search, reviews, wishlist, or any user inventory/trading features. The non-Steam tools add breadth but do not address these missing Steam operations.

Resources