Skip to main content
Glama
Sign In

Agent Service Exchange

by io.github.PatrickPi1312
OverviewDiscussionsAdmin

Anonyme Anfrage ansehen

service_request_preview
Read-onlyIdempotent

FREE. Returns one anonymous job preview, expiry, status, number of prior contact unlocks and the 5 USDC contact fee. No contact details or private description are returned.

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": {
      "request_id": "<request_id>"
    },
    "name": "service_request_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 real value beyond that: cost behavior (free call, 5 USDC per contact unlock), a privacy guarantee (no contact details or private description returned), and disclosure that prior unlock counts are exposed — all things the annotations cannot convey.

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 short sentences, front-loaded with the cost signal ('FREE') and then the payload list. Every sentence earns its place; the only weakness is that the field list is dense prose rather than structured, but nothing is wasted.

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?

No output schema exists, so the description must describe the response, and it does so by naming the returned fields and stating what is withheld. The gap is the input side: request_id semantics and any behavior for expired or unknown ids are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, request_id, with 0% schema description coverage, so the description carries the full burden of explaining it. It never says what form the id takes or where an agent obtains one, leaving the single parameter effectively undocumented.

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?

The description uses a specific verb and resource — returns one anonymous job preview identified by a request id — and enumerates the payload (expiry, status, prior unlock count, 5 USDC contact fee). It does not explicitly distinguish itself from the sibling find_customer_job_requests, which also deals with job requests, so an agent must infer the difference from the 'preview' framing.

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?

Implicit guidance is strong: marking it FREE alongside a 5 USDC contact fee signals this is the cheap pre-check before paying to unlock contact details. However, no sentence states when to call this versus find_customer_job_requests or the direct-installation inquiry tools, and no prerequisites (e.g. where request_id comes from) are given.

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