Zinvyl Marketplace Agent Gateway

Find the right Zinvyl service

find_service

Idempotent

Start here. Describe one authorized sanitized business need once. Zinvyl returns the best fixed-scope offer and exact next purchase action, or records an unsupported need as privacy-minimized product telemetry. It never treats a route, budget, or tool call as payment or contact permission.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`source`	No	Optional allowlisted source where the agent discovered Zinvyl.
`industry`	No	Optional broad industry only; do not name a person or confidential project.
`budget_cents`	No	Optional buyer-stated total budget in USD cents. This is demand telemetry, not spending authority or proof of funds.
`category_hint`	No
`agent_tool_type`	No		mcp_client
`request_summary`	Yes	One sanitized business outcome. Do not include names, email addresses, phone numbers, credentials, payment data, personal data, confidential text, or production secrets.
`turnaround_days`	No	Optional requested turnaround in calendar days.
`requested_output`	No	Optional sanitized deliverable type, such as weekly report or data export.
`authorized_to_share`	Yes	True only when the requester is authorized to share this sanitized need with Zinvyl for matching and aggregate product planning.
`near_match_offer_id`	No	Optional closest offer; it does not place unsupported work in scope.
`contains_no_personal_data_or_secrets`	Yes	True only after removing personal data, credentials, confidential material, and payment data.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

changedInput schema / properties / near_match_offer_id / enum

Previous value: -[
-  "zinvyl.venture.evidence-brief.v1",
-  "zinvyl.venture.prototype-scope.v1",
-  "zinvyl.freight.workflow-audit.v1",
-  "zinvyl.api.workflow-failure-rescue.v1",
-  "zinvyl.api.failure-triage.v1",
-  "zinvyl.freight.full-workflow-audit.v1"
-]New value: +[
+  "zinvyl.venture.evidence-brief.v1",
+  "zinvyl.venture.prototype-scope.v1",
+  "zinvyl.freight.workflow-audit.v1",
+  "zinvyl.api.workflow-failure-rescue.v1",
+  "zinvyl.api.failure-triage.v1",
+  "zinvyl.freight.full-workflow-audit.v1",
+  "zinvyl.content.ai-marketing-pilot.v1"
+]

AddedOct 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false and idempotentHint=true, and the description corroborates by disclosing that unsupported needs are recorded as privacy-minimized telemetry (a write) and that submission happens 'once' (idempotent). It also clarifies a non-obvious boundary: route, budget, or tool call is never treated as payment or contact permission. That is genuine context beyond the 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?

Three tight sentences, front-loaded with the routing cue 'Start here.' Every sentence carries content (entry positioning, return behavior, permission boundary) with no filler.

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?

There is no output schema, but the description compensates by describing what the call returns (best fixed-scope offer and next purchase action) and the fallback behavior. With 11 parameters at 82% schema coverage, an agent has enough to invoke it correctly.

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 82%, so the schema already documents the required authorization and sanitization flags and the optional fields. The description's 'one authorized sanitized business need' merely paraphrases the required parameters without adding format or constraint 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 outcome: submit one sanitized business need and receive the best fixed-scope offer plus the exact next purchase action, or have it recorded as telemetry. This distinguishes it from siblings like buy_service or prepare_purchase_route, though the 'Zinvyl' framing is jargon-heavy for an unfamiliar agent.

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?

'Start here' signals this is the entry point of the flow, which is real usage guidance. However, it never names an alternative among the many siblings (match_or_capture_demand, list_offers, qualify_task) or states when NOT to use it, so the agent must infer the routing.

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

All Zinvyl Marketplace Agent Gateway 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.

Resources

Need Help?