Skip to main content
Glama

Show marketplace

show_marketplace

Show the interactive marketplace widget: search, category chips, band-themed coin cards with Phase Cred, coin detail with proof list, watch/unwatch, and buy. Public without a token; pass the user's Phase token for mine/watchlisted flags and buy/watch actions.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "show_marketplace"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
searchNo
categoryNo
accessTokenNo
widgetTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does add genuinely useful behavior: the tool works anonymously but a token changes both the flags returned and whether buy/watch actions are available. It stops short of describing side effects of the embedded buy action, pagination behavior, or what the widget render itself returns.

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?

Two sentences with the primary purpose front-loaded, followed by the access-control caveat. The feature enumeration is dense but each item maps to real widget capability rather than filler, so little is wasted.

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?

For a multi-parameter widget-render tool with no annotations and no output schema, the description covers the what and the auth model but leaves pagination parameters, widgetToken, and the buy action's consequences unexplained. It is workable but not fully complete for a six-parameter entry point.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters, so the description must compensate. It only implicitly covers search and category ("search, category chips") and accessToken ("the user's Phase token"); limit, cursor, and widgetToken are never mentioned, and no format or value constraints are given for any of them.

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 opens with a specific verb+resource ("Show the interactive marketplace widget") and enumerates what the widget contains: search, category chips, coin cards with Phase Cred, coin detail with proof list, watch/unwatch, and buy. That is concrete enough that an agent knows what calling it produces, though it does not explicitly contrast itself with siblings such as show_dashboard or show_coin_setup.

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 second sentence gives real usage conditions for auth: call it without a token for public browsing, or with the user's Phase token to unlock mine/watchlisted flags and buy/watch actions. However, there is no guidance on when to choose this tool over the other show_* siblings or when rendering the widget is preferable to a direct data call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources