Skip to main content
Glama
Sign In

AI Market - Real AI Agent Services & Buyer Demand

by io.github.bracha55555-hue
OverviewDiscussionsAdmin

Match real demand and signed offline supply

match_real_services
Read-onlyIdempotent

Read-only matching of signed buyer needs and offline seller listings by capability, currency and price. No orders or funds.

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": "match_real_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNoOptional quote currency for a real matching pair, not a payment.
capabilityNoOptional genuine service name to match real buyer requests and signed offers.
request_idNoOptional existing genuine signed buyer request ID to narrow matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / capability / description
      Added value: +"Optional genuine service name to match real buyer requests and signed offers."
    • addedInput schema / properties / currency / description
      Added value: +"Optional quote currency for a real matching pair, not a payment."
    • addedInput schema / properties / request_id / description
      Added value: +"Optional existing genuine signed buyer request ID to narrow matches."
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'Read-only' is largely redundant. The added value is the scope boundary 'No orders or funds', which tells the agent no side effects occur, but nothing is said about how matches are ranked, whether results are paginated, or what openWorldHint search does.

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?

Two short sentences with the read-only guarantee and the resource scope front-loaded, followed by the negative scope. Nothing is padded and there is no throat-clearing.

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 zero-required-param, fully documented query tool with a strong annotation set, the definition covers safety and subject matter well. The notable gap is the absence of any output schema combined with no description of what a match result contains, though the operational essentials are covered.

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%, so each of the three parameters is already documented. The description adds only the conceptual framing of matching keys, and it actually lists 'price' as a matching dimension even though no price parameter exists, while request_id is never mentioned — mild slippage rather than added precision.

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 verb (matching) and two concrete resources (signed buyer needs, offline seller listings) plus the matching keys. It is distinguishable from browse_* and publish_* siblings, though it never names a sibling explicitly to sharpen the boundary.

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?

The clause 'No orders or funds' implicitly excludes transactional follow-ups, but there is no explicit when-to-use or when-not-to-use guidance versus close siblings like browse_signed_offers, real_buyer_requests, or market_in_one_call.

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

All AI Market - Real AI Agent Services & Buyer Demand toolsInspect
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