Skip to main content
Glama
Sign In
gamelibs-mcp

gamelibs-mcp

by AliSoftware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

steam_resolve_user

Resolve any Steam vanity slug or profile URL to its numeric SteamID64, enabling accurate API lookups and game library queries.

Instructions

Resolve a Steam vanity slug or profile URL to a SteamID64.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vanity_or_url": "<vanity_or_url>"
    },
    "name": "steam_resolve_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
vanity_or_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full behavioral burden. It states the core transformation and the accepted input shapes, but does not disclose behavior on invalid vanity names, error conditions, rate limits, or the exact return representation.

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?

A single, front-loaded sentence contains the entire contract with no filler. Every word adds semantic content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter resolver, the description is nearly sufficient: it defines input variants and the output type. The main missing piece is the exact return shape (string vs object) since there is no output schema, but the tool is simple enough that an agent can invoke it correctly from this definition.

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?

The schema provides no property description (0% coverage), so the description must clarify the parameter. It does: 'vanity_or_url' is a vanity slug or profile URL, which gives the agent the essential value format. It could be improved with examples or handling of trailing slashes, but it is substantially more meaningful than the raw 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 names a specific verb ('Resolve'), a precise input ('Steam vanity slug or profile URL'), and an unambiguous output ('SteamID64'). It is distinct from sibling tools that list or fetch game details rather than convert identifiers.

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 explicit when-to-use guidance or exclusions are provided; the tool does not mention alternatives or conditions under which it should be preferred. The intended use is inferable from the name and purpose, but the description itself carries no usage direction.

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