App News
app_newsRead-onlyIdempotent
App news feed.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| appid | Yes | ||
| count | No | ||
| maxlength | No |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| appnews | No |
Steam
TDQS
D1.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds no behavioral context beyond what annotations already provide. While annotations (readOnlyHint, idempotentHint, etc.) indicate a safe read operation, the description does not disclose what the news feed contains, how results are paginated, or any other operational details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short, but this is under-specification rather than conciseness. It is a single noun phrase that provides minimal information, similar to a low-quality label rather than a useful tool description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is incomplete given its parameters and sibling context. There is no explanation of what 'news' refers to, how appid is used, or what the output represents. Even with an output schema present, the description fails to provide enough context for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description must compensate by explaining parameters, but it does not. The schema lists appid, count, and maxlength without any descriptions, and the description offers no hints about their meaning or usage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'App news feed' essentially restates the tool name and title without using a specific verb like 'get' or 'list'. It gives a vague sense that the tool returns news items for an app, but does not clearly distinguish it from sibling tools such as app_details or app_list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives. The description does not mention any prerequisites, scenarios, or exclusions, leaving the agent to infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
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.