Skip to main content
Glama

list_local_meetings

Read-onlyIdempotent

Lists all active local CLI-based meetings so you can track ongoing Claude CLI sessions.

Instructions

List all active LOCAL meetings (CLI-based).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description contributes the 'active' filtering behavior and the local/CLI scope, which is real added context, but says nothing about result shape, ordering, or what happens when no meetings exist.

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 short sentence with the scope qualifier front-loaded and no wasted words. The parenthetical '(CLI-based)' is slightly cryptic but functional.

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?

For a zero-parameter read-only listing tool with rich annotations and no output schema, almost everything an agent needs to call it correctly is present. Only the meaning of 'active' and the returned fields remain underspecified, which is minor at this complexity.

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 no parameters, so the schema has nothing to explain and the baseline is 4. The description correctly signals a no-argument, list-everything call rather than suggesting filters that do not exist.

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 verb and resource ('List all active LOCAL meetings') plus a scope qualifier ('CLI-based'), which lets an agent distinguish it from the sibling list_meetings. It stops short of naming that sibling explicitly, so the differentiation is implied by capitalization 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: 'active' suggests it excludes finished meetings, and 'LOCAL/CLI-based' suggests a local-execution context. There is no explicit when-to-use or when-to-prefer-list_meetings guidance, so the agent must infer the boundary from the adjective alone.

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