Skip to main content
Glama

Steam

by io.github.pipeworx-io
OverviewDiscussionsAdmin

App News

app_news
Read-onlyIdempotent

App news feed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appidYes
countNo
maxlengthNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
appnewsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "appid": 730
+  },
+  {
+    "appid": 570,
+    "count": 5,
+    "maxlength": 300
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "appnews": {
+      "properties": {
+        "appid": {
+          "description": "App ID",
+          "type": "number"
+        },
+        "count": {
+          "description": "News item count",
+          "type": "number"
+        },
+        "newsitems": {
+          "items": {
+            "properties": {
+              "appid": {
+                "description": "App ID",
+                "type": "number"
+              },
+              "author": {
+                "description": "News author",
+                "type": "string"
+              },
+              "contents": {
+                "description": "News content",
+                "type": "string"
+              },
+              "date": {
+                "description": "Unix timestamp",
+                "type": "number"
+              },
+              "feed_type": {
+                "description": "Feed type",
+                "type": "number"
+              },
+              "feedlabel": {
+                "description": "Feed label",
+                "type": "string"
+              },
+              "feedname": {
+                "description": "Feed name",
+                "type": "string"
+              },
+              "gid": {
+                "description": "News item ID",
+                "type": "string"
+              },
+              "is_external_url": {
+                "description": "Is external link",
+                "type": "boolean"
+              },
+              "title": {
+                "description": "News title",
+                "type": "string"
+              },
+              "url": {
+                "description": "News URL",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

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.

All Steam toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources