Skip to main content
Glama

Steam

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

TDQS

A4.7/5.0
Behavior5/5

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

Adds scoping to user identifier (anonymous IP, BYO key hash, or account ID) and the omit-key-to-list behavior, going beyond the readOnly/idempotent annotations; no contradiction.

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?

Two dense, front-loaded sentences conveying purpose, usage, scoping, and workflow without 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 tool with one param and no output schema, the description adequately covers purpose, usage, scoping, and companion tools, making it complete enough for effective selection and invocation.

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 already fully documents the key parameter with 100% coverage; description reinforces the omit-to-list behavior but adds little beyond the schema's own description.

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?

States it retrieves a value saved via remember or lists all saved keys, using specific verb+resource and distinguishing from sibling remember/forget tools.

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 provides when to use (look up saved context like ticker/address/notes) and mentions companion tools remember/forget, giving clear guidance vs alternatives.

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