get_conceptReturns a detailed explanation for a Steam / steamwebapi concept (identifiers, CS2 mechanics, pricing fields, inventory flags). Built from curated domain knowledge specific to this platform.
| Name | Required | Description | Default |
|---|---|---|---|
| term | Yes | Concept name or alias, e.g. "assetid", "doppler phase", "market_hash_name", "pricelatest". |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that the explanation is built from curated domain knowledge, indicating a static knowledge base rather than a live API call. This adds valuable context, even though it does not cover error handling or response formatting.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single well-structured sentence that is front-loaded with the primary action and outcome. It contains no redundant phrasing and earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter lookup tool with no output schema, the description is complete: it states what is returned, the scope of the knowledge, and the platform-specific nature. There are no significant gaps for an agent to select and invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% because the sole parameter 'term' has a detailed description with examples. The tool description further adds the domain scope (identifiers, CS2 mechanics, pricing fields, inventory flags), which helps users understand what terms are valid, going slightly beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states it returns a detailed explanation for a Steam/steamwebapi concept, and specifically lists categories (identifiers, CS2 mechanics, pricing fields, inventory flags). This distinguishes it from siblings like list_concepts (which lists concepts) and search_endpoints (which searches endpoints).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The context is clear: use this tool when you need a detailed explanation of a specific concept. It does not explicitly mention alternatives or exclusions, but the distinct purpose and sibling names imply the appropriate usage scenario.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource/action: execution, concept lookup, endpoint spec, pricing, and enumeration of games, markets, products, endpoints, and concepts. No overlapping purposes.
All tools follow a consistent verb_noun snake_case pattern (call_, get_, list_, search_), making the naming predictable and easy to navigate.
10 tools is well-scoped for an API exploration server, covering execution, lookup, search, enumeration, and pricing without redundancy.
The server covers the full workflow: discover endpoints, search concepts, list supported games/markets/products, retrieve detailed specs and pricing, and execute readonly API calls. No obvious gaps for its intended purpose.