Skip to main content
Glama

list_calendar_names

Retrieve the names of all calendars available on your Mac. Use this to identify calendars for event management and scheduling.

Instructions

List available calendars

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.js:20-20 (registration)
    Tool 'list_calendar_names' is registered as part of the TOOLS array (line 20), with description 'List available calendars'. It is then registered via server.tool() in the loop at lines 106-110. This is a stub server—the real implementation is a native binary.
    ["list_calendar_names", "List available calendars"],
  • The handler function for list_calendar_names (and all tools) is a stub async function that returns a static text response. The real implementation exists in a separate native binary.
    for (const [name, desc] of TOOLS) {
      server.tool(name, desc, {}, async () => ({
        content: [{ type: "text", text: "This is an inspection stub. Install Local MCP: npx -y local-mcp@latest setup" }],
      }));
    }
Behavior2/5

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

No annotations are provided, and the description only states 'List available calendars'. It does not disclose that the tool is read-only, what the output format is (e.g., names only or full objects), or any side effects. The agent is left to guess behavioral traits.

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, which is concise but perhaps too minimal. It is front-loaded but could benefit from a bit more detail, such as what is returned.

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 tool with no parameters and no output schema, the description is minimally complete. However, it does not specify the return format (e.g., calendar names, IDs) or that the tool returns all available calendars. An agent might need to infer functionality from the name alone.

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 has no parameters, and schema coverage is 100% (empty schema). The description does not need to add parameter info, so baseline of 4 is appropriate.

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 'List available calendars' clearly states the action (list) and the resource (calendars), matching the tool name exactly. It distinguishes from siblings like list_calendar_events, so purpose is unambiguous.

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

Usage Guidelines4/5

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

No explicit usage guidance is given, but the tool is simple and there are no similar siblings that list calendars (only list_calendar_events). Implied usage is clear, but the description could mention that this is a prerequisite for other calendar operations.

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/lanchuske/local-mcp-releases'

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