pulsenetwork

gamepulse

GamePulse: Gaming economy intelligence — play, trade, earn. Live in-game item (skins) prices across Steam Market and Skinport with real cash-out math, Roblox niche viability with live player data, creative-skill earnings maps, game deals, buy-or-wait verdicts, meta analysis, TCG valuations, esports intelligence.

Coverage: Global

Endpoints: • skin-check ($0.05): Live skin/item price check with cash-out math • roblox-check ($0.25): Roblox niche viability check with live data • earn-map ($0.15): Creative-skill earnings map for the games industry • deals ($0.05): Game deals • worth-it ($0.08): Buy or wait verdict • meta ($0.08): Game meta analysis • trending ($0.05): Trending games • setup ($0.10): PC gaming setup • price ($0.10): Card price analysis • invest ($0.15): Set investment analysis • deal ($0.15): eBay card deal finder • matches ($0.05): Esports matches • team ($0.08): Esports team profile • betting ($0.10): Esports betting analysis • tournament ($0.10): Tournament breakdown • portfolio ($0.10): Trading card portfolio valuation • achievements ($0.08): Achievement hunting guide • specs ($0.08): PC compatibility check • subscription ($0.08): Gaming subscription value calculator • time ($0.05): Game completion time estimator

Input Schema

TableJSON Schema

Name	Required	Description
`cpu`	No	CPU model
`gpu`	No	GPU model
`ram`	No	RAM (GB)
`set`	No	set
`card`	No	card
`game`	No	cs2 (default), dota2, rust, tf2
`item`	No	Item name — exact Steam market_hash_name works best, fuzzy accepted
`lang`	No	Response language (default en)
`name`	No	name
`cards`	No	Comma-separated card list
`games`	No	Comma-separated games you play
`genre`	No	e.g. rpg, action, strategy, fps
`match`	No	match
`niche`	No	Game niche keyword, e.g. tycoon, obby, horror, pet simulator
`skill`	No	music, audio, art, 3d, writing, animation, code, voice, video
`action`	Yes	Which endpoint to call. Options: skin-check \| roblox-check \| earn-map \| deals \| worth-it \| meta \| trending \| setup \| price \| invest \| deal \| matches \| team \| betting \| tournament \| portfolio \| achievements \| specs \| subscription \| time
`budget`	No	Budget in USD ($200-$10,000)
`achievement`	No	Specific achievement (optional)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 12, 2026

changedInput schema / properties / item / description

Previous value: -"Item name, e.g. AK-47 | Redline (Field-Tested)"New value: +"Item name — exact Steam market_hash_name works best, fuzzy accepted"

changedInput schema / properties / niche / description

Previous value: -"Niche keyword, e.g. tycoon, obby, horror"New value: +"Game niche keyword, e.g. tycoon, obby, horror, pet simulator"

Changed6 schema fields changedJul 11, 2026

changedInput schema / properties / action / description

Previous value: -"Which endpoint to call. Options: deals | worth-it | meta | trending | setup | price | invest | deal | matches | team | betting | tournament | portfolio | achievements | specs | subscription | time"New value: +"Which endpoint to call. Options: skin-check | roblox-check | earn-map | deals | worth-it | meta | trending | setup | price | invest | deal | matches | team | betting | tournament | portfolio | achievements | specs | subscription | time"

changedInput schema / properties / action / enum

Previous value: -[
-  "deals",
-  "worth-it",
-  "meta",
-  "trending",
-  "setup",
-  "price",
-  "invest",
-  "deal",
-  "matches",
-  "team",
-  "betting",
-  "tournament",
-  "portfolio",
-  "achievements",
-  "specs",
-  "subscription",
-  "time"
-]New value: +[
+  "skin-check",
+  "roblox-check",
+  "earn-map",
+  "deals",
+  "worth-it",
+  "meta",
+  "trending",
+  "setup",
+  "price",
+  "invest",
+  "deal",
+  "matches",
+  "team",
+  "betting",
+  "tournament",
+  "portfolio",
+  "achievements",
+  "specs",
+  "subscription",
+  "time"
+]

changedInput schema / properties / game / description

Previous value: -"Game title or slug e.g. elden-ring, cyberpunk-2077"New value: +"cs2 (default), dota2, rust, tf2"

addedInput schema / properties / item

Added value: +{
+  "description": "Item name, e.g. AK-47 | Redline (Field-Tested)",
+  "type": "string"
+}

addedInput schema / properties / niche

Added value: +{
+  "description": "Niche keyword, e.g. tycoon, obby, horror",
+  "type": "string"
+}

addedInput schema / properties / skill

Added value: +{
+  "description": "music, audio, art, 3d, writing, animation, code, voice, video",
+  "type": "string"
+}

First observedJul 6, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the burden and does disclose pricing per endpoint, coverage scope, and data sources like Steam Market and Skinport. However, it omits behavioral details such as error handling, rate limits, or whether any actions have side effects, and it does not explicitly state that all endpoints are read-only.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a concise opening statement and a clearly formatted endpoint list with prices. Each line is purposeful given the 20 sub-endpoints, though the length is substantial.

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 tool with 18 parameters and 20 endpoints, the description lacks a mapping between actions and required/enabled parameters, which is critical for correct invocation. It also doesn't describe return formats or handling of invalid actions, leaving an agent to guess at endpoint-param relationships.

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?

The input schema covers all 18 parameters, and the description adds a domain context for some actions (e.g., skin-check relates to item), but it does not map which parameters are required for each action. Weak schema entries like 'set', 'card', 'name', and 'match' remain unexplained, and the description doesn't compensate for this ambiguity.

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 identifies GamePulse as a gaming economy intelligence tool with specific verbs like 'skin-check' and 'roblox-check' covering global data. It distinguishes from sibling pulse tools by focusing on gaming use cases, though it bundles 20 endpoint actions under one umbrella rather than a single specific function.

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?

The description provides a strong implied usage context ('gaming economy intelligence') and enumerates endpoint categories, but it never explicitly states when to prefer this tool over a sibling or when not to use it. There are no exclusions or alternative tool references, leaving usage guidance implicit.

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

All pulsenetwork tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

gamepulse

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources