Skip to main content
Glama

Zinvyl Marketplace Agent Gateway

List Zinvyl fixed-scope offers

list_offers
Read-onlyIdempotent

Use when comparing Zinvyl's full 18-option catalog. For a single sanitized need, start with read-only qualify_task. Returns price, delivery window, required inputs, exclusions, and direct intake URL; use get_acceptance_tests only after selecting an offer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered; the description adds the return payload and its position in the qualification→selection→acceptance workflow. It does not say whether the catalog is static or how the 18 options are ordered, but with a fixed-size catalog that is a minor gap.

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?

Two dense sentences, front-loaded with the triggering condition and followed by return contents and the next-step boundary. Every clause carries routing or payload information; nothing is redundant or padded.

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?

There is no output schema, so the description must and does describe return values, and annotations handle the safety semantics. An agent has enough to decide when to call it, what it gets back, and what to call next.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly implies a parameterless catalog listing. No parameter meaning is lost because there is nothing to specify.

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?

The description states concretely what comes back (price, delivery window, required inputs, exclusions, intake URL) and frames the tool as the way to compare the full 18-option catalog. It explicitly distinguishes itself from qualify_task (single need) and get_acceptance_tests (post-selection), so an agent can identify this tool without opening a schema.

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?

Explicit when-to-use (comparing the whole catalog), an explicit alternative for the narrow case (a single sanitized need → qualify_task), and an explicit ordering constraint (only call get_acceptance_tests after selecting an offer). The routing is complete enough that no inference is required.

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