Skip to main content
Glama
Sign In
Anam MCP Server

Anam MCP Server

Official
by anam-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_meeting_bots

List recent Recall meeting bots and view their status and meeting URLs. Adjust the limit to control results.

Instructions

List all Recall meeting bots.

Shows recent bots including their status and meeting URLs.

Args: limit: Maximum number of bots to return (default: 20)

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_meeting_bots"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.13

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so the description must fully disclose behavior. It only states it lists recent bots; missing details on read-only nature, pagination, authentication needs, and what 'recent' means. Insufficient for a tool with no annotations.

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?

The description is extremely concise: two lines for purpose and one line for the parameter, with no redundancy. It front-loads the key action and result.

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

Completeness3/5

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

For a simple list tool with one optional parameter and an output schema, the description is adequate but not complete. It lacks details on ordering, handling large lists, and safety guarantees, which would be expected given no annotations.

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 0%, but the description adds meaning to the 'limit' parameter by explaining it controls the maximum number of bots returned. However, it does not elaborate on format or constraints beyond the default.

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 resource 'Recall meeting bots', and specifies that it shows recent bots with status and meeting URLs. This distinguishes it from siblings like 'get_meeting_bot_status' which focuses on a single bot.

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 explicit guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or contrast with listing other resources like sessions or avatars.

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