agent-health

create_utility_account

Create once with an optional unique username (3–48 letters/digits/_/-); omit it to use the stable account ID. Immediately save the private API key and reuse it for every utility request. Identity follows the key; username is a self-declared private label, not a login or recovery credential. Read utility_account to resume; never create a fresh account for each task. 500-credit monthly balance top-up through December 2026; read pricing for current policy. No automatic billing or health registration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_utility_account"
  }
}

Input Schema

Name	Required	Description	Default
`username`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

addedInput schema / properties / username

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Username"
+}

AddedSep 11, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only declare it is a non-destructive write with open-world scope; the description goes well beyond by disclosing the key-handling contract (save the private API key immediately, identity follows the key), that username is not a login or recovery credential, and the credit/billing posture (500-credit monthly top-up, no automatic billing, no health registration). These are exactly the behavioral facts an agent cannot get from the annotations.

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?

Front-loaded with the verb, the one-time constraint, and the key-handling imperative, and each sentence is substantive. The credit-policy sentence ('500-credit monthly balance top-up through December 2026') is tangentially related, date-bound, and will go stale, which slightly dilutes an otherwise tight definition.

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 single-parameter creation tool whose annotations already cover the safety profile and which has an output schema covering returns, the description supplies everything else an agent needs: one-time-use rule, key persistence, identity model, and how to resume.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden and does: it constrains format (3–48 chars, letters/digits/_/-) and explains the semantics of omission (falls back to the stable account ID). It also clarifies that the value is a self-declared private label rather than an identity credential.

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 and resource ('Create ... account') plus scope ('once') and names the sibling that handles resumption ('Read utility_account to resume'), so the agent can distinguish it from utility_account and set_utility_identity without opening 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?

Gives explicit when-to-use ('create once', omit username for default), explicit when-not ('never create a fresh account for each task'), and the alternative ('Read utility_account to resume'). Nothing is left to inference.

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

All agent-health tools Inspect

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

Need Help?