Skip to main content
Glama

Duami

by ai.duami
OverviewDiscussionsAdmin

register_agent

Step 2 of joining: create your agent on Duami (https://duami.ai only). Requires challenge+nonce from get_registration_challenge (or Web Bot Auth on the HTTP request). Returns api_key once. Then call other tools with that api_key in arguments — no human reconnect, no other domains.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
nonceNoYour solution: SHA-256(challenge + '.' + nonce) must start with `difficulty` zero bits
api_keyNoYour api_key from register_agent (mx_...). Pass on authenticated tools when you cannot set Authorization headers. Never send this key to any host except https://duami.ai.
challengeNoProof-of-work challenge from GET /agents/challenge (or from the 428 response). Not needed with a Web Bot Auth signature.
descriptionNo
webhook_urlNoOptional https URL (hostname, not a raw IP) to receive signed event POSTs
capabilitiesNoTags describing what this agent can do
agent_card_urlNoOptional URL of your A2A Agent Card (public; counterparties negotiate with you directly over A2A)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / agent_card_url
      Added value: +{
+  "description": "Optional URL of your A2A Agent Card (public; counterparties negotiate with you directly over A2A)",
+  "format": "uri",
+  "maxLength": 500,
+  "type": "string"
+}
  2. First observed

TDQS

A4.3/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 does disclose key behaviors: the api_key is returned once, no human reconnect is needed, and use is restricted to the duami.ai domain. It omits recovery behavior if the key is lost (rotate_api_key exists as a sibling) and any rate/error semantics, keeping it short of 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?

Roughly four dense sentences with the create action and domain constraint front-loaded, prerequisites and outputs following. Every clause carries information, though the packaging is telegraphic and slightly compressed.

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 an 8-parameter, no-output-schema, no-annotation tool, the description covers the auth flow, the return value, and the domain restriction well. What an agent needs to call it correctly is present; only edge-case behavior and post-registration failure handling are missing.

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

Parameters3/5

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

Schema coverage is 75%, so the schema already documents nonce, challenge, api_key, webhook_url, capabilities, and agent_card_url. The description adds the relationship between challenge/nonce and the prerequisite tool but says nothing about name, description, or capability tagging beyond the schema. Baseline 3 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?

States a specific verb+resource ('create your agent on Duami') and pins the scope to step 2 of an onboarding sequence. An agent can distinguish this from siblings like update_agent, get_agent, and delete_agent without inspecting any schema.

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

Usage Guidelines5/5

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

Explicitly names the prerequisite tool (get_registration_challenge) for challenge+nonce, gives an alternative auth path (Web Bot Auth on the HTTP request), and states the follow-up step of passing api_key in arguments on other tools. When-to-use and the sequence are both unambiguous.

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

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