Skip to main content
Glama
Sarg338

Steam MCP

by Sarg338
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

steam_get_steam_level

Read-only

Get a Steam user's XP-based community level by SteamID, vanity name, or profile URL. Returns human-readable markdown or JSON.

Instructions

Get a user's Steam community level (the XP-based account level).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.18.0
    • removedInput schema / $defs / PlayerInput / properties / response_format / $ref
      Removed value: -"#/$defs/ResponseFormat"
    • addedInput schema / $defs / PlayerInput / properties / response_format / enum
      Added value: +[
+  "markdown",
+  "json"
+]
    • addedInput schema / $defs / PlayerInput / properties / response_format / type
      Added value: +"string"
    • removedInput schema / $defs / PlayerInput / properties / steamid / default
      Removed value: -null
    • removedInput schema / $defs / PlayerInput / properties / steamid / title
      Removed value: -"Steamid"
    • removedInput schema / $defs / PlayerInput / title
      Removed value: -"PlayerInput"
    • removedInput schema / $defs / ResponseFormat
      Removed value: -{
-  "description": "Output format for tool responses.",
-  "enum": [
-    "markdown",
-    "json"
-  ],
-  "title": "ResponseFormat",
-  "type": "string"
-}
    • removedInput schema / title
      Removed value: -"steam_get_steam_levelArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "steam_get_steam_levelOutput",
-  "type": "object"
-}New value: +null
  2. First observedv1.14.0

TDQS

C2.8/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. With readOnlyHint=true, the agent knows it's safe, but the description does not disclose potential errors (e.g., private profile), rate limits, or other behavioral traits. It merely restates the purpose.

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 a single, clear sentence that states the core purpose. It is concise and front-loaded with the key information. Every word earns its place.

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?

For a getter with no output schema, the description should explain what the return value looks like or at least provide usage context. It does neither. The schema covers parameters, but the description lacks guidance on when to use this tool or what to expect in the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool description does not mention any parameters. Schema description coverage is 0%, so the description should compensate for the lack of parameter explanation. The schema itself has detailed descriptions for steamid and response_format, but the tool description adds no value in helping the agent understand parameter usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and the resource 'user's Steam community level' with a clarifying parenthetical. It is specific enough to understand the tool's purpose, but it does not explicitly differentiate from siblings like steam_get_player_summary which might also include level information.

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?

No usage guidance is provided. The description does not mention when to use this tool over alternatives, nor does it suggest any context where this should not be used. There is no mention of prerequisites or related tools.

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

Deploy Server

Other Tools