Skip to main content
Glama
Sign In
SteamDT MCP Server

SteamDT MCP Server

by zkcaryq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

steamdt_get_price_single

Retrieve real-time buy and sell prices for a specific Steam item across multiple platforms using its market hash name.

Instructions

通过 marketHashName 查询单品在各平台的在售/求购价格。频率限制 60次/分钟。

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": {
      "marketHashName": "<marketHashName>"
    },
    "name": "steamdt_get_price_single"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketHashNameYesSteam 官方饰品名称，可从 base_info 获取

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Only discloses rate limit, not other behavioral traits like authentication needs, data freshness, or read-only nature.

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 focused sentences with no unnecessary words, efficiently conveying purpose and constraint.

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

Completeness3/5

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

Covers basic function and frequency limit, but lacks output description (structure of price data per platform) since no output schema exists.

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 coverage is 100%. Description adds that marketHashName is the official Steam item name and obtainable from base_info, providing helpful context beyond the 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 clearly states the tool queries selling/buying prices for a single item across platforms using marketHashName, distinguishing it from batch or average price tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly mentions a frequency limit of 60 times/minute, but provides no guidance on when to use versus alternatives like batch or average price 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