Zero to Hundred marketplace

Compare marketplace software

z2h_compare_marketplace_listings

Read-onlyIdempotent

Compare a shortlist of public software from marketplace search. Returns current public descriptions, USD license prices, types and tech stacks. Unavailable software is omitted without disclosing its status. This tool cannot purchase software or access private source.

Input Schema

Name	Required	Description	Default
`slugs`	Yes	Listing identifiers to compare, in the order the Buyer wants them presented. Copy each slug from z2h_search_marketplace.

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 / slugs / description

Previous value: -"Shortlist from marketplace search, in the desired comparison order."New value: +"Listing identifiers to compare, in the order the Buyer wants them presented. Copy each slug from z2h_search_marketplace."

First observedOct 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Goes beyond the readOnly/idempotent annotations by disclosing that unavailable software is silently dropped without status disclosure — a genuinely non-obvious behavior an agent must account for in reporting. Also bounds the tool with "cannot purchase software or access private source." Minor gap: no guidance on what happens if all slugs are unavailable.

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?

Three tight sentences, zero filler. The capability statement comes first, followed by return contents, then behavioral caveats — a clean front-loaded structure.

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 an output schema, full parameter descriptions, and rich annotations, the description covers what remains: scope of data returned and the silent-omission behavior. It leaves out error handling for invalid or non-public slugs, which is the only meaningful residual gap.

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% and already documents minItems 2 / maxItems 4 and the ordering semantics, so the schema does the heavy lifting. The description's word "shortlist" only loosely echoes the array constraint and adds no new syntax or format detail.

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?

States a specific verb (compare) and resource (public marketplace software shortlist) plus what the response contains: descriptions, USD license prices, types, tech stacks. It is clearly distinguishable from z2h_search_marketplace (discovery) and z2h_get_listing (single fetch).

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

Usage Guidelines4/5

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

Anchors usage to "a shortlist of public software from marketplace search," implying it is the follow-up step after search and before a decision. It does not explicitly name when to use z2h_get_listing instead, so it falls short of the full when/when-not/alternatives bar.

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.