Skip to main content
Glama

Search Nexez offers

nexez_search
Read-only

Find services or products for a specific buyer request. Returns JSON text with ranked results, structured offers, listing slugs, agent.json URLs, and applied filters. Use nexez_directory for broad browsing, then nexez_get_page to inspect an exact offer before a dry run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "nexez_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesWhat the buyer is looking for
limitNoMaximum results; defaults to 10 and is rounded down and clamped to 1-50.
categoryNoMarketplace category; omit or use all to include both professional and consumer listings.
industryNoCase-insensitive substring filter on the published industry, for example plumbing.
locationNoOptional city/region filter
verifiedNoFilter by seller verification signal: true requires a signal, false requires its absence; omit to include both.
min_trustNoMinimum marketplace trust score (0-100); omit for no trust threshold. Not a guarantee of seller performance.
price_bandNoFilter by the listing marketplace price band. Inspect the exact offer for its price and currency; this is not a checkout quote.
min_readinessNoMinimum listing readiness score (0-100); omit for no readiness threshold.
supports_checkoutNoDeprecated compatibility filter: any actionable offer or provider handoff
nexez_checkout_readyNoOwner payout state confirms Nexez-settled checkout readiness
supports_negotiationNoFilter by negotiation availability: true for eligible listings, false for non-negotiable listings; omit to include both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / lat
      Removed value: -{
      -  "description": "Optional latitude context metadata. Does not filter or rerank results; use location for geographic filtering.",
      -  "type": "number"
      -}
    • removedInput schema / properties / lng
      Removed value: -{
      -  "description": "Optional longitude context metadata. Does not filter or rerank results; use location for geographic filtering.",
      -  "type": "number"
      -}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), so the description's added value is the return shape: ranked results, structured offers, listing slugs, agent.json URLs, applied filters. That is genuinely useful because there is no output schema, though pagination, result-count behavior, and empty-result handling are unstated.

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 sentences, zero filler: purpose first, return payload second, sibling routing third. Nothing is repeated from the schema or annotations.

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?

For a 12-parameter search with no output schema, the description covers purpose, response shape, and navigation to adjacent tools, with the schema carrying all parameter detail. Only minor operational gaps remain, such as how filters combine and what a zero-result response looks like.

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% and the schema itself explains defaults, clamping, enum meanings, and caveats like 'not a checkout quote' and the deprecated supports_checkout flag. The description adds little parameter-level meaning beyond 'applied filters' appearing in the response, so the schema is doing the heavy lifting.

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 services or products') scoped to a buyer request, and explicitly contrasts with the two nearest siblings (nexez_directory for broad browsing, nexez_get_page for inspecting an exact offer). An agent can pick this tool without opening any schema.

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?

Clearly routes the agent: broad browsing belongs to nexez_directory, exact-offer inspection belongs to nexez_get_page. What's missing is an explicit when-not condition for this tool itself (e.g., what queries should skip search entirely), and 'before a dry run' is never defined.

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