Zero to Hundred marketplace

Search marketplace software

z2h_search_marketplace

Read-onlyIdempotent

Find live software by keyword before building from scratch. Public, no sign-in needed. Returns descriptions, USD license prices, tech stacks and listing links. Example: {"search": "invoice", "limit": 5}. Empty search browses recent software. When hasMore is true without nextCursor, narrow the search. Matching is lexical. Errors set isError; retry a rate limit later. Use z2h_compare_marketplace_listings for a shortlist or z2h_show_marketplace for cards. A result does not guarantee suitability or purchase availability.

Input Schema

Name	Required	Description
`mode`	No	Filter by the listing's sale model. Omission leaves the sale model unfiltered.
`sort`	No	Result order. Defaults to relevance for a search, otherwise newest.
`type`	No	Categories matching the kind of software the Buyer wants. Omission searches across categories.
`limit`	No	Number of listings to return in this page. Omission uses 20.
`cursor`	No	Opaque nextCursor from the previous page. Keep the same filters and sort.
`search`	No	Keywords describing the software the Buyer needs.
`domains`	No	Industry tags for the software. Choose keys from the Zero to Hundred taxonomy: ai, analytics, art-design, auth-identity, cms, conference, developer-tools, devops, e-commerce-marketplace, education, entertainment, environmental, fashion, finance, food, gaming, graphic-design, health, interior-design, marketing, membership, messaging, non-profit, political, productivity, real-estate, religious, services, social, technology, travel, ux-ui, wedding, other. Omission searches across industries.
`operatingStatus`	No	Filter by software readiness or existing commercial operation, rather than listing publication state.

Output Schema

Name	Required	Description
`hasMore`	Yes	More matches exist. If nextCursor is null, narrow the search instead of paging.
`results`	Yes	Live public software matching the filters.
`nextCursor`	Yes	Cursor for the next page, or null if cursor paging is unavailable or finished.
`searchMode`	Yes	Text uses keyword matching, not semantic similarity.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 27, 2026
- removedOutput schema / properties / nextCursor / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / nextCursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- 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"
+]
```

Changed6 schema fields changedOct 16, 2026

changedInput schema / properties / domains / description

Previous value: -"Industry domain keys, such as finance. Omit to search all domains."New value: +"Industry tags for the software. Choose keys from the Zero to Hundred taxonomy: ai, analytics, art-design, auth-identity, cms, conference, developer-tools, devops, e-commerce-marketplace, education, entertainment, environmental, fashion, finance, food, gaming, graphic-design, health, interior-design, marketing, membership, messaging, non-profit, political, productivity, real-estate, religious, services, social, technology, travel, ux-ui, wedding, other. Omission searches across industries."

changedInput schema / properties / limit / description

Previous value: -"Listings per page. Defaults to 20."New value: +"Number of listings to return in this page. Omission uses 20."

changedInput schema / properties / mode / description

Previous value: -"License listing mode filter. Omit for all supported modes."New value: +"Filter by the listing's sale model. Omission leaves the sale model unfiltered."

changedInput schema / properties / operatingStatus / description

Previous value: -"Software operating states to include, independent of listing publication status."New value: +"Filter by software readiness or existing commercial operation, rather than listing publication state."

changedInput schema / properties / search / description

Previous value: -"Buyer need or software keyword. Search is lexical, not semantic."New value: +"Keywords describing the software the Buyer needs."

changedInput schema / properties / type / description

Previous value: -"Software categories to include. Omit for all categories."New value: +"Categories matching the kind of software the Buyer wants. Omission searches across categories."

First observedOct 16, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent/open-world, and the description adds substantial non-annotation context: no sign-in required, what fields come back, lexical (not semantic) matching, a pagination gotcha ('hasMore true without nextCursor' means narrow the query), error/rate-limit retry behavior, and a suitability disclaimer. This is exactly the kind of operational detail structured fields cannot carry.

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?

Front-loaded with the purpose in the first clause, then packed with high-value operational facts in terse sentences. No filler; nearly every sentence maps to a distinct agent decision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter read-only search with an output schema, this covers intent, example invocation, result contents, pagination edge case, error handling, and sibling routing. Nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds a concrete call example ({"search": "invoice", "limit": 5}), clarifies that an omitted search browses recent items, and ties 'lexical' matching to the search param and nextCursor to the cursor param. It doesn't clarify the interaction of sort defaults with the filter arrays, so it stays just above baseline rather than excelling.

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 and resource ('Find live software by keyword') and immediately frames the decision it supports ('before building from scratch'). It also explicitly separates itself from z2h_compare_marketplace_listings (shortlist) and z2h_show_marketplace (cards), so an agent can route without opening schemas.

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 explicit when-to-use reasoning ('before building from scratch'), names two alternative siblings with the condition that selects each, and covers the degenerate case ('Empty search browses recent software'). Exclusions and the fallback path are both stated.

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.