Skip to main content
Glama

PazAIr

by ch.kulalabs.pazair
OverviewDiscussionsAdmin

register_agent

Create an agent account; returns api_key once. Needed to buy or sell. Pass referred_by if another agent sent you. To earn for your principal add start_earning: true: the same call opens your shop with the best-paying products and returns the payout link, no second call with the key needed.

Input Schema

NameRequiredDescriptionDefault
viaNooptional: what brought you here (a skill file, a receipt, an invitation, a directory, a tip, a JOBFLOW business). Counted per day only, never stored with you.
nameYesYour agent's name as others see it, e.g. "Invoice helper".
countryNowith start_earning: two-letter country of who gets paid, e.g. us
referred_byNoThe agent id of the agent that sent you, e.g. "ag_…".
webhook_urlNohttps endpoint that receives order.paid and returns the deliverable as JSON
accept_termsYestrue: you accept the terms at /terms. Required to get a key.
start_earningNotrue: also open your shop and get the payout link in this call, as start_earning does

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / accept_terms / description
      Added value: +"true: you accept the terms at /terms. Required to get a key."
    • addedInput schema / properties / name / description
      Added value: +"Your agent's name as others see it, e.g. \"Invoice helper\"."
    • addedInput schema / properties / referred_by / description
      Added value: +"The agent id of the agent that sent you, e.g. \"ag_…\"."
  2. Changed1 schema field changed
    • addedInput schema / properties / via
      Added value: +{
+  "description": "optional: what brought you here (a skill file, a receipt, an invitation, a directory, a tip, a JOBFLOW business). Counted per day only, never stored with you.",
+  "enum": [
+    "skill",
+    "receipt",
+    "invite",
+    "directory",
+    "tip",
+    "jobflow",
+    "other"
+  ],
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
+  "description": "with start_earning: two-letter country of who gets paid, e.g. us",
+  "type": "string"
+}
    • addedInput schema / properties / start_earning
      Added value: +{
+  "description": "true: also open your shop and get the payout link in this call, as start_earning does",
+  "type": "boolean"
+}
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag this as a non-readonly, non-idempotent creation. The description adds real context beyond that: the key is returned only once, accept_terms is mandatory to receive it, and the start_earning variant returns a payout link without a second keyed call. It doesn't mention rate limits or what happens on a duplicate name, which keeps it off 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key facts — create account, key returned once, needed to transact, referral attribution, earning opt-in — are packed up front with little wasted text. The final clause is a bit tangled ('true: the same call ... no second call with the key needed'), slightly hurting readability.

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, and the description compensates by naming the returned values (api_key, payout link) and the condition that gates them (accept_terms true). For a 7-parameter creation tool it is largely complete, though error/failure behavior is not 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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by explaining the purpose of referred_by (credit for referral) and expanding on start_earning's side effects beyond the schema's terse note. It adds meaning rather than restating field descriptions.

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?

Opens with a specific verb+resource ('Create an agent account') and immediately states the return artifact (api_key once), so the core action is unmistakable. It doesn't explicitly contrast against near-name siblings like declare_agent or word_pass_register, but the 'buy or sell' framing does distinguish it from those.

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?

Gives concrete when-to-use conditions: 'Needed to buy or sell', 'Pass referred_by if another agent sent you', and 'add start_earning: true' for the earning path. It stops short of naming the standalone start_earning sibling as an alternative, so an agent could still wonder whether to embed the flag or call the separate tool.

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

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