Skip to main content
Glama
Sign In

Agent Service Exchange

by io.github.PatrickPi1312
OverviewDiscussionsAdmin

Passende Kundenanfragen finden

find_customer_job_requests
Read-onlyIdempotent

FREE. Searches open customer job requests by trade and area for service businesses seeking work. Returns anonymous previews without customer contact details. The planned contact unlock price is 5 USDC, without a job guarantee; payment availability is reported separately.

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": {
      "trade": "<trade>",
      "country": "<country>",
      "region": "<region>"
    },
    "name": "find_customer_job_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo
tradeYes
regionYes
countryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/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 real value beyond that: results are anonymized previews without contact details, contact unlock is planned at 5 USDC with no job guarantee, and payment availability is reported separately. It stops short of describing pagination behavior or result volume, so it is strong but not complete.

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?

Four compact sentences, front-loaded with the FREE qualifier and the core purpose. Every sentence adds information; only the payment-availability clause feels slightly tangential but it is still decision-relevant.

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

Completeness3/5

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

No output schema exists, so the description must convey return shape; it does partially (anonymous previews, no contact details) but says nothing about result count, ordering, or how to page with after/limit. For a 5-parameter, 0%-coverage tool this leaves real gaps.

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 description coverage is 0%, so the description carries the burden. "by trade and area" maps loosely to trade and region/country, but no format guidance is given (country codes? region names?), and the after cursor and limit parameters are not mentioned at all in the description.

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 and resource: "Searches open customer job requests by trade and area," plus who it is for ("service businesses seeking work"). An agent can tell this is a discovery/lead-finding tool, though it never names the sibling it contrasts with, e.g. find_service_providers being the mirror operation.

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?

Implies usage by naming the audience and the two filters, and flags the search as FREE, which helps an agent decide to call it before any paid step. However there is no explicit when-to-use/when-not guidance and no reference to alternative sibling tools such as service_request_preview or find_service_providers.

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

All Agent Service Exchange 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