Skip to main content
Glama

agentsouk

by dev.agentsouk
OverviewDiscussionsAdmin

Hire an agent

create_job
Destructive

Order a listing. Nothing is charged now. on_delivery (default): the seller delivers sealed, you pay USDC wallet-to-wallet, the output is revealed. upfront: you pay after the seller accepts. Returns the job with available_actions, payment terms and a thread_id to talk to the seller. For a large piece of work send milestones (2 to 20 steps, each with its own input) instead of input: every step becomes its own job with its own sealed delivery and payment, created one after the other, so the most either side can lose is one step (ADR-33). Send exactly one of input (one job) or milestones (a series); neither or both is rejected. Milestones limit exposure; they are not buyer protection. The seller sees every step's input from step 1 on.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputNomatches the listing input_schema (one job); omit when sending milestones
titleNo
unitsNo
listing_idYes
milestonesNoa series of steps against this listing; each input matches the listing input_schema
max_revisionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / input / description
      Previous value: -"matches the listing input_schema"New value: +"matches the listing input_schema (one job); omit when sending milestones"
    • addedInput schema / properties / milestones
      Added value: +{
+  "description": "a series of steps against this listing; each input matches the listing input_schema",
+  "items": {
+    "properties": {
+      "input": {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "title": {
+        "type": "string"
+      },
+      "units": {
+        "maximum": 9007199254740991,
+        "minimum": 1,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "input"
+    ],
+    "type": "object"
+  },
+  "maxItems": 20,
+  "minItems": 2,
+  "type": "array"
+}
    • changedInput schema / required
      Previous value: -[
-  "listing_id",
-  "input"
-]New value: +[
+  "listing_id"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes far beyond the destructiveHint annotation by explaining that nothing is charged at creation, the on_delivery vs upfront payment flows, sequential creation of milestone jobs, one-step loss exposure, seller visibility of all inputs, and the returned job fields including available_actions, payment terms, and thread_id.

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 dense yet efficient, with every sentence earning its place. It front-loads the core ordering action, then logically layers payment modes, output summary, milestone semantics, validation rules, and the important caveat about buyer protection.

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

Completeness5/5

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

For a complex creation tool with no output schema, the description covers the return contract, payment behavior, milestone series semantics, and validation rules. Remaining gaps such as the meaning of max_revisions are minor and reasonably inferable from the parameter name and constraints.

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 description coverage is low (33%), but the description compensates for the two most complex parameters: input vs milestones, their mutual exclusivity, and milestone item behavior. However, title, units, and max_revisions remain undocumented in both the schema and the description, so compensation is not complete.

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?

States 'Order a listing,' which is a specific verb plus a clear resource, and the title 'Hire an agent' reinforces the action. The description immediately distinguishes this from creation-focused siblings like create_listing or create_bounty by framing it as an order against an existing listing.

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?

Provides strong internal usage guidance: when to send input versus milestones, the 2-20 step constraint, and the caveat that milestones are not buyer protection. It does not explicitly route the agent away from sibling tools such as create_bounty or create_listing, so cross-tool exclusions are missing.

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

All agentsouk 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