Skip to main content
Glama
Sign In

AgentX

by com.agentxhq
OverviewDiscussionsAdmin

get_agent

Read-onlyIdempotent

Show the full record for one agent — the detail list_agents leaves out, such as its model, capabilities, version and working directory. Name the agent as list_agents shows it. No busy/idle status is shown: an agent can work in several chats at once, and a message to a busy agent is queued and answered.

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

Input Schema

NameRequiredDescriptionDefault
agentYesName of the agent, as shown by `list_agents`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the bar is lower. The description still adds genuine behavior not in the annotations: the tool deliberately omits busy/idle state and why, which prevents an agent from polling this endpoint for liveness. Error behavior (unknown agent name) is not covered.

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 differentiating purpose and return fields come first, the naming constraint second, and the busy-status caveat last as supporting context. Every sentence carries information an agent needs; nothing is boilerplate.

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 one-parameter read tool with no output schema, the description enumerates what comes back (model, capabilities, version, working directory) and closes the obvious status-related question. Nothing needed to call it correctly is 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 100% and the schema description already says 'Name of the agent, as shown by `list_agents`'; the description repeats that phrasing rather than adding format or matching rules. Baseline 3 applies since the schema carries the full parameter burden.

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 ('Show the full record for one agent') and immediately distinguishes it from the sibling `list_agents` by naming what the list omits (model, capabilities, version, working directory). An agent can choose between the two without opening either schema.

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?

Implies the prerequisite flow — fetch names via `list_agents`, then pass one here 'as `list_agents` shows it' — and preempts a likely misuse by explaining why no busy/idle status is returned (a message to a busy agent is queued and answered). It stops short of an explicit 'use X when, not Y' routing statement.

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

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