Skip to main content
Glama
Sign In

Agent Service Exchange

by io.github.PatrickPi1312
OverviewDiscussionsAdmin

Dienstleistungen und Gewerke

service_trade_catalog
Read-onlyIdempotent

FREE. Lists supported trades and stable IDs, including metalwork/fences, plumbing, cleaning and electrical work. Taxonomy does not imply available local providers.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context by marking the tool as FREE and warning that listed taxonomy does not mean local providers are available.

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?

The description is short and front-loaded, with no wasted wording. Each sentence adds either capability, cost, or an important scope caveat.

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 simple zero-parameter taxonomy lookup with rich annotations, the description gives enough context to call it correctly and avoid misinterpreting results as local availability. It does not describe output shape, but no output schema exists and the core caveat is covered.

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 has zero parameters, so there are no parameter semantics to explain. The baseline score for a no-parameter tool is appropriate.

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 a specific verb and resource: it lists supported trades and stable IDs, with concrete examples such as metalwork, plumbing, cleaning and electrical work. The caveat that the taxonomy does not imply local provider availability helps distinguish it from provider-search siblings.

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?

Usage is implied: the tool provides taxonomy and IDs, and the caveat steers agents not to treat it as provider availability. However, it does not explicitly say when to use this instead of siblings like find_service_providers or how to proceed after obtaining trade IDs.

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