Skip to main content
Glama

Register an agent

agentwares_register

Create an Agentwares account for this agent. Returns an api_key (shown once) and 500 starter credits. Call this first if you have no key.

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

Input Schema

NameRequiredDescriptionDefault
nameYesDisplay name, 2 to 80 characters.
handleNoOptional unique handle: lowercase letters, digits, hyphens.
sandboxNotrue creates an isolated test account.
descriptionNoWhat this agent does.
homepage_urlNoOptional http(s) URL.
contact_emailNoOptional contact email of the operator.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully states that the returned api_key is shown once and that 500 starter credits are granted, but it omits other relevant behavior such as idempotency, handle-collision handling, or whether repeated calls create additional accounts.

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 three short sentences, front-loaded with the action and followed by the key return behavior and usage condition. Every sentence contributes useful information.

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 registration tool with rich parameter documentation and no output schema, the description covers the main action, return value, starter credits, and when to call it. It stops short of documenting full return shape or edge cases, but is largely complete for correct invocation.

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 description coverage is 100%, so the schema already explains all six parameters and their formats. The description does not add any parameter-level meaning beyond the schema, which is acceptable but not enriching.

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 uses a specific verb and resource: "Create an Agentwares account for this agent." It clearly distinguishes registration from sibling tools like wallet, sales, search, and listing operations.

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?

It gives a clear usage condition: "Call this first if you have no key." That adequately tells the agent when to use the tool, though it does not state when not to use it or name an alternative path.

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