Zero to Hundred marketplace

Show marketplace software

z2h_show_marketplace

Read-onlyIdempotent

Show public software cards and an interactive comparison panel. First search with z2h_search_marketplace, then pass the public slugs to display, and the search text you used as search so the panel shows what the cards are for. Without slugs, shows the newest live software. Prices and availability are refreshed on the server. Listing links open the Zero to Hundred website.

Input Schema

Name	Required	Description	Default
`slugs`	No	Search-result slugs to show. Omit to display the newest live software.
`search`	No	Text to prefill the panel's search box. Use the query that produced the supplied slugs. Cards are selected by slugs; this text does not filter them.

Output Schema

Name	Required	Description
`hasMore`	Yes	This response contains the complete refreshed selection.
`results`	Yes	Current live software, in selection order when slugs were supplied.
`nextCursor`	Yes	Selection refreshes do not paginate. Use marketplace search for paging.
`unavailableSlugs`	Yes	Requested slugs unavailable publicly. Their private status is never disclosed.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026
- removedOutput schema / properties / results / items / properties / licensePrice / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / results / items / properties / licensePrice / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / search / description

Previous value: -"Search text displayed in the panel. It does not filter these cards; supply search-result slugs too."New value: +"Text to prefill the panel's search box. Use the query that produced the supplied slugs. Cards are selected by slugs; this text does not filter them."

First observedOct 16, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world behavior, so the bar is lower. The description still adds useful context beyond them: prices and availability are refreshed server-side, and listing links open the external Zero to Hundred website — behavior an agent could not infer from structured fields.

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?

Front-loads what is rendered, then the workflow, then defaults and side notes. Every sentence carries information, though the closing sentence about listing links is slightly tangential and could be tightened.

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?

An output schema exists, so return values need not be described, and the description covers the search-then-show workflow, the empty-input default, and server-side refresh. Only the distinction from z2h_compare_marketplace_listings is left unaddressed.

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%, so both parameters are already fully documented in the schema, and the description largely restates that slugs select the cards and search only prefills the panel. It adds the rationale for passing the originating query, but no syntax or format detail beyond the schema.

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?

States a specific verb and resource — renders public software cards plus an interactive comparison panel — and gives the default behavior (newest live software when no slugs). It hints at a prerequisite relationship with z2h_search_marketplace but never explicitly contrasts itself with the similar-sounding z2h_compare_marketplace_listings sibling.

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?

Gives an explicit sequence: search first with z2h_search_marketplace, then pass the resulting public slugs here. It also states the no-argument path (omit slugs to show the newest live software), so both branches of use are covered without inference.

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

All Zero to Hundred marketplace 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.