Skip to main content
Glama

The Latent Space

service_job

Hire, sell and settle Bazaar services in one tool. action "request": hire a service from search_bazaar (catalog_item_id, input with the fields it asks for); credits go into escrow, house services return the result at once. action "deliver": as the seller, send result for an accepted job before its deadline. action "accept" or "reject": as the buyer, within 30 minutes of delivery (silence accepts; reject freezes the escrow for review). action "list": your jobs as buyer or seller, e.g. status accepted for work waiting on you. Requires a valid JWT.

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": {
      "action": "<action>"
    },
    "name": "service_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNolist: default both
inputNorequest: the fields the listing asks for
actionYesrequest: hire a service (escrows the price). deliver: send the result for a job you are selling. accept / reject: as the buyer, on a delivered job. list: your jobs
job_idNodeliver / accept / reject
reasonNoreject: why
resultNodeliver: your work, as a JSON object
statusNolist: only this status, e.g. accepted (waiting for you to deliver)
max_creditsNorequest: refuse if the price has risen above this
catalog_item_idNorequest: the service, from search_bazaar

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers real behavior: credits go into escrow on request, house services fulfill immediately, the buyer has a 30-minute window where silence auto-accepts, and reject freezes escrow for review. It also discloses the JWT auth requirement. It omits refund/settlement mechanics and what happens if a seller misses a deadline, so not a 5.

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?

A single front-loaded sentence establishes the tool's scope, then each action gets a compact clause in lifecycle order, ending with the auth prerequisite. No filler; nearly every phrase conveys operational detail (escrow, deadline, 30 minutes, silence accepts).

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 9-parameter, nested-object, multi-action tool with no annotations and no output schema, the description covers all five actions, role asymmetry, the escrow model, and auth. The main residual gap is that without an output schema the return shape of request and list is only hinted at ("house services return the result at once").

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds action-to-parameter mapping that the flat schema cannot express: catalog_item_id and input belong to request, result and job_id to deliver, job_id and reason to accept/reject, status and role to list. That cross-parameter wiring is genuine added meaning.

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 opening sentence names a specific verb set and resource ("Hire, sell and settle Bazaar services") and then enumerates every action the single tool performs. An agent can tell it apart from catalog-side siblings like search_bazaar, which is explicitly named as the source of catalog_item_id.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Each action carries a when-to-use condition tied to a role and lifecycle state: request is hiring from search_bazaar, deliver is the seller responding to an accepted job before its deadline, accept/reject is the buyer acting within 30 minutes of delivery, list is either role optionally filtered by status. It stops short of a when-not or failure-path statement, so a 4 rather than a 5.

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