Skip to main content
Glama
us-all

openmetadata-mcp-server

by us-all

list-bots

Retrieve paginated lists of bots, with options to filter fields and include deleted entities.

Instructions

List bots with pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoComma-separated fields to include
limitNoNumber of results per page
beforeNoCursor for backward pagination
afterNoCursor for forward pagination
includeNoInclude deleted entitiesnon-deleted

Implementation Reference

  • Zod schema for list-bots input: fields, limit (default 10), before/after cursors, include (default non-deleted).
    export const listBotsSchema = z.object({
      fields: z.string().optional().describe("Comma-separated fields to include"),
      limit: z.coerce.number().optional().default(10).describe("Number of results per page"),
      before: z.string().optional().describe("Cursor for backward pagination"),
      after: z.string().optional().describe("Cursor for forward pagination"),
      include: z.enum(["non-deleted", "deleted", "all"]).optional().default("non-deleted").describe("Include deleted entities"),
    });
  • Async handler that calls GET /bots with the input params via omClient.
    export async function listBots(params: z.infer<typeof listBotsSchema>) {
      return omClient.get("/bots", params);
    }
  • src/index.ts:417-417 (registration)
    Tool registration: tool('list-bots', ...) using listBotsSchema.shape and wrapToolHandler(listBots).
    tool("list-bots", "List bots with pagination", listBotsSchema.shape, wrapToolHandler(listBots));
  • Import of listBotsSchema and listBots from ./tools/bots.js.
    import { listBotsSchema, listBots, getBotSchema, getBot, getBotByNameSchema, getBotByName } from "./tools/bots.js";
Behavior2/5

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

No annotations exist, so the description must convey behavioral traits. It mentions pagination but fails to state that this is a read-only operation, or describe any side effects, data limits, or authentication needs. The schema already documents pagination parameters.

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?

The description is a single, short sentence that conveys the core purpose immediately. It is front-loaded and efficient, though it could benefit from a bit more context without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero annotations, no output schema, and many similar siblings, the description is too minimal. It does not explain the return format, pagination mechanics, or how fields/parameters like include affect results, leaving gaps for the agent.

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% with descriptions for each parameter. The description adds no extra meaning beyond what the schema provides, meeting the baseline of 3 for adequate schema coverage.

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?

The description clearly states the verb 'List' and the resource 'bots', and specifies 'with pagination'. This distinguishes it from siblings like get-bot or get-bot-by-name, and aligns with the pagination parameters in the schema.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus other list-* tools or get-bot variants. There are many sibling list tools without differentiation, leaving the agent without context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/us-all/openmetadata-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server