Skip to main content
Glama

list_published_agents

Read-onlyIdempotent

Retrieve and display all published agents available for chat so users can identify and select an agent to interact with.

Instructions

List published agents available for chat

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
agentsNo
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.3
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "anyOf": [
      +    {
      +      "required": [
      +        "success",
      +        "agents"
      +      ]
      +    },
      +    {
      +      "properties": {
      +        "error": {
      +          "additionalProperties": true,
      +          "properties": {
      +            "code": {
      +              "type": "string"
      +            },
      +            "message": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "code",
      +            "message"
      +          ],
      +          "type": "object"
      +        },
      +        "success": {
      +          "const": false
      +        }
      +      },
      +      "required": [
      +        "success",
      +        "error"
      +      ],
      +      "type": "object"
      +    }
      +  ],
      +  "properties": {
      +    "agents": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "bio": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "commercial_name": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "id"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the meaningful scope filter (only published, chat-available agents are returned), but says nothing about ordering, result limits, or whether unpublished/draft agents are excluded by policy versus permissions.

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?

A single seven-word sentence with no filler, and the scope qualifier 'published ... available for chat' is front-loaded where it matters most. It is efficient but borders on under-specified rather than deliberately tight.

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?

The tool is trivial (no parameters), has a rich annotation set, and ships an output schema, so the description needn't explain return shape or safety. What remains missing is minor: expected result ordering/size and the explicit contrast with list_agents, neither of which prevents correct invocation.

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 document and the baseline of 4 applies. Nothing in the description misrepresents or invents 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 specific verb-resource pair ('List published agents') plus a scope qualifier ('available for chat'), which distinguishes it from the generic sibling list_agents. It stops short of explicitly naming list_agents as the unfiltered alternative, so differentiation is implied by the adjective 'published' rather than stated.

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?

Usage is only implied: an agent can infer this is the read path to find chat-capable agents versus the broader list_agents, and the natural follow-on is chat_with_agent. There is no explicit when-to-use/when-not statement or named alternative, so the agent must infer the routing from sibling names.

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