Skip to main content
Glama

AINDEX

An agent's own tools

list_agent_tools
Read-only

Every tool one of your agents has, with its input schema: reading its account and fills, placing and closing orders on Lighter and Hyperliquid (decide), swaps and lending on Robinhood Chain, moving money between venues, writing its standing strategy (set_strategy), making markets (set_quotes). Call any of them with call_agent_tools. Needs the owner's access 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": {
      "agent": "<agent>"
    },
    "name": "list_agent_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYes
names_onlyNoOnly the names and descriptions, without schemas.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with that, so no contradiction exists. The one real addition is 'Needs the owner's access key', an authentication prerequisite the annotations do not convey; however, it says nothing about result ordering, pagination, or how tools from unconnected venues are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core statement is front-loaded, which is good, but the middle clause is a dense run-on enumerating venue and category examples that reads like a capability catalog rather than a tool description. The key call-to-action and auth note are buried at the end instead of being given their own prominence.

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 read-only, two-parameter discovery tool with no output schema, the description covers what is returned (tool names plus input schemas), the auth requirement, and the next step via call_agent_tools. It is close to complete; minor gaps remain around result scope and whether all agent-authored tools are included.

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 50%: names_only is documented in the schema, while the required agent parameter (with only a pattern) is not. The description implies the agent parameter via 'one of your agents' and the 'with its input schema' phrasing hints at what names_only toggles, adding modest meaning beyond the schema but not compensating fully for the undocumented required parameter.

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 opening clause 'Every tool one of your agents has, with its input schema' gives a clear verb-plus-resource and makes it obvious how this differs from the sibling call_agent_tools, which merely invokes the returned tools. The long parenthetical enumerating categories (orders, swaps, lending, set_strategy, set_quotes) describes what the agent's tools can do rather than what this tool does, which slightly dilutes the purpose statement.

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?

'Call any of them with call_agent_tools' gives an explicit follow-up route and names the alternative tool, which is genuinely useful guidance. It does not state when to prefer this over list_my_agents or get_my_agent, nor does it exclude any conditions, so it stops short of full when/when-not coverage.

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