Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

steam_search

Search the Steam store by title to resolve game names to app IDs, prices, platforms, and metascores, returning roughly ten matching apps.

Instructions

Search the Steam store by title. Resolves a search term to Steam apps via the store typeahead (title, appid, price, platforms, metascore). Best for title -> appid lookup; returns roughly ten results. For faceted, paginated search use /steam/search/results.

Input Schema

NameRequiredDescriptionDefault
lNoLanguage code
ccNoStore country code (ISO, selects currency)
termYesSearch term

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description still discloses the typeahead mechanism, approximate result count, and returned fields. It does not cover auth, rate limits, or locale/country effects, but for a read-only search endpoint the key behavioral traits are present.

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 definition is four short sentences, front-loads the core purpose, and uses the final sentence efficiently to route agents to the correct alternative. There is no redundant or filler text.

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?

With no output schema, the description usefully lists returned fields and the approximate result count. It leaves minor gaps around locale/country effects and exact response shape, but is otherwise complete for a simple search tool.

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 description coverage is 100%, so the baseline is 3. The description adds that the search term is a title, but it does not explain how l or cc affect language, country, or currency beyond what the schema already says.

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 states a specific verb and resource: searching the Steam store by title and resolving a term to Steam apps. It adds concrete result content (title, appid, price, platforms, metascore) and clearly distinguishes this from faceted search by pointing to /steam/search/results.

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

Usage Guidelines5/5

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

It explicitly says this is best for title-to-appid lookup and notes roughly ten results are returned. It also names the alternative for faceted, paginated search, giving the agent a clear routing rule.

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