Skip to main content
Glama

Check calendar status

get_feed_status
Read-onlyIdempotent

Reads a selected feed’s last update, current subscription availability (distribution_ready), editing access and configured monitoring status for a requested status check. This does not refresh, save or charge. Scope is limited to the connected account’s Smart Calendars AI feeds. No mailbox access, source-document retrieval, automatic source monitoring, scheduled PDF checks or document refresh is provided. Structured schedule content is supplied explicitly by the caller. Result links: subscription_open_url is the exact HTTPS handoff to the default calendar app via webcal; subscription_options_url provides Apple/default, Google, Outlook and copy-link choices; subscription_url is the copyable HTTPS calendar-file fallback; manage_url opens the feed dashboard. URL hosts, paths and tokens identify the returned resource and are not interchangeable. A filtered_subscription has its own links for that selection; top-level links remain unfiltered. Subscription access requires distribution_ready=true. Opening a link does not confirm a subscription; confirmation occurs in the user’s calendar app.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "feed_id": "<feed_id>"
    },
    "name": "get_feed_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
feed_idYesIdentity of the selected calendar returned in feed results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / feed_id / description
      Added value: +"Identity of the selected calendar returned in feed results."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds real substance beyond them: the distribution_ready=true gate for subscription access, and the crucial caveat that opening a link does not confirm a subscription (confirmation happens in the user's calendar app). It also explains that URLs are resource-identifying and not interchangeable, which the annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Scope and the non-refresh caveat are front-loaded, which is good, but the middle is a long negative enumeration ('No mailbox access, source-document retrieval, automatic source monitoring, scheduled PDF checks or document refresh') and the link taxonomy is dense. Every clause is defensible on its own, yet the paragraph exceeds what a 1-parameter read tool needs to convey.

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

Completeness5/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 carry the return shape, and it does: it names distribution_ready, editing/monitoring status, top-level vs filtered_subscription link sets, and defines each URL's intended destination. An agent has everything needed to call the tool and interpret the response.

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?

Schema coverage is 100% for the single parameter, so the schema already documents feed_id as a UUID taken from feed results. The description reinforces provenance ('selected feed', 'returned in feed results') but adds no format or syntax detail, so the baseline-plus rather than a top score 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?

States a specific verb and resource ('Reads a selected feed's last update, current subscription availability..., editing access and configured monitoring status'), which separates it from get_feed (full record) and list_feeds (enumeration) in the sibling set. The agent can tell exactly what class of data comes back without opening a schema.

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?

Explicit negative scoping ('does not refresh, save or charge', no mailbox access, no source retrieval, no scheduled checks) tells the agent when this tool is the wrong pick, and 'Scope is limited to the connected account's Smart Calendars AI feeds' bounds applicability. It never names a sibling alternative, so it stops short of a full when/when-not/alternative triad.

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