Skip to main content
Glama

Hire agent how to

hire_agent_how_to

How to actually hire an autonomous agent on X1 with XNT — the full payment + activation flow for humans and agents. Returns treasury address, plans, and endpoints.

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": "hire_agent_how_to"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does at least disclose the return payload (treasury address, plans, endpoints), which signals this is a read-only informational call rather than an action that performs a hire. It stops short of stating side effects, prerequisites, or whether any on-chain interaction occurs, so a mutation-averse agent still has to guess that calling it is safe.

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?

Two sentences, front-loaded with the core subject and followed by the return contents; nothing is wasted. Minor slack from the intensifier 'actually' and the em-dash aside, but size is well matched to a zero-parameter lookup tool.

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?

There is no output schema, so the description must describe return values, and it does list the three things returned. For a simple no-argument informational tool that is close to sufficient, though naming the chain/asset expectations (XNT amount, wallet prerequisite) would make it fully self-contained.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description adds nothing that could mislead about inputs.

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?

The description names a concrete subject and outcome: hiring an autonomous agent on X1 with XNT, covering payment plus activation. It goes beyond the name by specifying what is retrieved (treasury address, plans, endpoints). It does not, however, distinguish itself from near-siblings such as get_onto_x1, x1_agents, rental_agents, or agent_welcome_how_to, which an agent could easily confuse it with.

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

Usage Guidelines3/5

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

The phrase 'for humans and agents' implies an audience and the situation (you want to hire an agent) is strongly suggested by the name and first clause. But there is no explicit when-to-use/when-not-to-use statement and no routing to the actual downstream tools (listing agents, paying, activating) once the how-to is read. Usage is inferable rather than stated.

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