Skip to main content
Glama
Sign In
Metrx MCP Server

Metrx MCP Server

by metrxbots
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Agents

metrx_list_agents
Read-onlyIdempotent

List all AI agents in your organization, including status, category, and cost, and optionally filter by status or category to retrieve agent IDs for other tools.

Instructions

List all AI agents in your organization with their status, category, and cost. Optionally filter by status or category. Returns agent IDs needed for other tools. Do NOT use for detailed per-agent analysis — use get_agent_detail for that. Requires an API key with the 'read' scope.

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

Input Schema

NameRequiredDescriptionDefault
statusNoFilter by agent status
categoryNoFilter by agent category (e.g., "sales", "support", "engineering")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered; the description adds value beyond them with an auth requirement ('API key with the read scope') and the fact that returned IDs feed other tools. It omits pagination, result-size limits, and ordering behavior.

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?

Four short sentences, front-loaded with the resource and return fields, then filters, then the sibling exclusion, then the auth prerequisite. No sentence is padding.

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?

No output schema exists, and the description partially compensates by naming returned fields and the agent IDs other tools need. For a simple two-optional-filter list tool this is nearly complete; pagination/result-count behavior is the one remaining gap.

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% with an enum for status and examples for category, so the schema already carries full parameter meaning. The description only restates that filtering exists, adding no syntax or semantics beyond the schema — baseline 3.

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 ('List all AI agents in your organization') plus the fields returned (status, category, cost), and explicitly distinguishes itself from metrx_get_agent_detail. An agent can tell it apart from siblings without opening a 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?

Explicitly names the case it is NOT for ('detailed per-agent analysis') and routes to metrx_get_agent_detail, and states the optional filtering. The positive case (need an org-wide overview / IDs) is only implied rather than spelled out, so not quite a 5.

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

Deploy Server

Other Tools