Skip to main content
Glama
khushalB-sf

calendar-mcp

by khushalB-sf
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Server Quality Checklist

67%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v1.0.0

  • Disambiguation4/5

    The two tools are distinct: one lists meetings, the other shows free/busy availability. While both relate to the calendar for a given day, their descriptions clearly differentiate the outputs.

    Naming Consistency5/5

    Both tool names follow the 'get_' prefix with a clear noun phrase (todays_meetings, availability). The naming pattern is consistent and predictable.

    Tool Count3/5

    With only two tools, the server feels under-scoped for a calendar integration. However, the narrow focus on read-only queries makes the count somewhat acceptable, though it is on the thin side.

    Completeness2/5

    The tool surface lacks any CRUD operations for meetings (create, update, delete) and only provides read-only queries. This is a significant gap for a calendar MCP server, as agents cannot manage calendar events.

  • Average 3.8/5 across 2 of 2 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 1 commit in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior3/5

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

    No annotations are present, so the description bears the full disclosure burden. It does reveal several behaviors: it limits results to 'working hours,' uses the 'Microsoft 365 calendar' as the data source, and defaults to today. Yet it doesn't disclose the output format, timezone handling, or how working hours are determined, leaving notable gaps.

    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 two sentences, front-loaded with the core action and scope, and contains no filler. Every word contributes to understanding the tool's purpose and default behavior.

    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 read-only tool with three optional, well-documented parameters and no output schema, the description covers purpose, scope, and default. However, without annotations or an output schema, it leaves out return-format details and lacks any positioning against the sibling tool, making it only minimally complete for agent use.

    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?

    The input schema provides 100% coverage for all parameters, so the baseline is 3. The description adds minimal parameter-related meaning beyond what the schema already states—only reinforcing 'given day' and 'Defaults to today,' which are already documented on the date parameter.

    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?

    The description uses a specific verb ('Report') and a clear resource ('free and busy time within working hours... based on the Microsoft 365 calendar'), making the tool's function easy to grasp. It implies a distinction from the sibling tool 'get_todays_meetings' by focusing on general daily availability rather than today's meetings, but it doesn't explicitly name the alternative.

    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?

    The description states it reports availability for 'a given day' and 'Defaults to today,' giving the agent a clear sense of when to use the tool. However, it doesn't provide explicit when-to-use versus when-not-to-use guidance or reference the sibling tool 'get_todays_meetings' as an alternative.

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

  • Behavior3/5

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

    No annotations are provided, so the description must carry the burden. It indicates a read-only operation ('List'), notes that it operates on the signed-in user's calendar, and mentions default date behavior. However, it does not disclose return format, pagination, or any limitations, which would be useful for a tool without 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 a single focused sentence (two clauses) that immediately states the action and scope, with no redundant information.

    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 simple tool with one optional parameter and no output schema, the description covers the core behavior and default. It could be more complete by describing the return structure or noting any restrictions, but it is adequate for basic use.

    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% (the only parameter 'date' is fully described with pattern and default). The description adds no new semantic meaning beyond the schema, so baseline 3 applies.

    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 a specific verb ('List') and resource ('meetings on the signed-in user's Microsoft 365 calendar for a given day'), distinguishing it from the sibling tool get_availability which likely returns availability slots rather than meeting details.

    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?

    The description gives clear context (listing meetings for a day, with default to today), but does not explicitly mention when to use this instead of get_availability, so it lacks explicit exclusion/alternative guidance.

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

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

calendar-mcp MCP server

Copy to your README.md:

Score Badge

calendar-mcp MCP server

Copy to your README.md:

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/khushalB-sf/calendar-mcp'

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