Skip to main content
Glama

Describe what an AI agent is made of

get_bot_schemas
Read-onlyIdempotent

Describe what an AI agent is made of. Every configuration section, flow step kind and rule condition an AI agent can use, each with English and Spanish labels and its JSON Schema, plus the models an agent may run on and which of the bot features this account has. A form or flow editor can be generated from it without knowing any kind in advance. Administrators only..

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional: return only these fields of each record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fields / items / enum
      Previous value: -[
      -  "sections",
      -  "steps",
      -  "conditions",
      -  "builtins",
      -  "tool_input_schema",
      -  "models",
      -  "default_model",
      -  "question_sets",
      -  "features",
      -  "decisions_mode"
      -]New value: +[
      +  "sections",
      +  "steps",
      +  "conditions",
      +  "builtins",
      +  "tool_input_schema",
      +  "models",
      +  "default_model",
      +  "question_sets",
      +  "features",
      +  "voice_engines",
      +  "decisions_mode"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/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 description's added value is the "Administrators only" permission requirement and the disclosure that the payload is a static, account-scoped catalog. That is meaningful context beyond the structured fields. It does not discuss payload size or whether the catalog is cached/versioned, which would have pushed this higher.

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?

Three sentences, front-loaded with the core purpose and with the administrator restriction placed last where it is easy to spot. The middle sentence is dense but each clause names a distinct payload component rather than padding. Minor cost: the opening sentence duplicates the title.

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?

There is no output schema, so the description must characterize the return value — and it does so thoroughly, naming every major payload component and the bilingual labels. Combined with the admin-only note and full schema coverage on the one parameter, an agent has enough to call it correctly; only the `fields` filter is left implicit.

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 a single optional enum parameter `fields`, so the schema already documents its semantics. The description never mentions the parameter directly, though its enumeration of sections, steps, conditions, models and features implicitly maps onto the enum values. Baseline 3 is appropriate given the schema does the work.

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?

States a specific resource: the metamodel of an AI agent — configuration sections, flow step kinds, rule conditions, labels in English/Spanish, JSON Schema, available models and account features. This distinguishes it from the sibling tools, which fetch concrete bots, agents or reports rather than a kind catalog. The opening sentence largely restates the title, but the enumeration that follows carries the real meaning.

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?

"A form or flow editor can be generated from it without knowing any kind in advance" implies the use case (building a UI or validating kinds) and "Administrators only" sets a precondition. However, it never explicitly states when to call this instead of get_native_bot_definition or get_details_of_a_single_account_agent_bot, so the agent must infer the split between catalog lookup and instance lookup.

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