Skip to main content
Glama

company get calendar

company_get_calendar
Read-onlyIdempotent

Read the Agency Workspace calendar within a UTC date range. Optionally filter publishing/approval status and channelKey; follow nextCursor with unchanged filters. includeApproval opts in to approval fields.

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": {
      "workspaceId": "<workspaceId>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "company_get_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesExact UTC ISO instant, e.g. 2026-09-11T12:00:00.000Z. To publish now use the current time and retain it unchanged on retry
fromYesExact UTC ISO instant, e.g. 2026-09-11T12:00:00.000Z. To publish now use the current time and retain it unchanged on retry
limitNo
cursorNoOpaque nextCursor from the previous page; keep every other filter unchanged
statusesNo
channelKeyNoExact channel key from company_list_channels, not the connection database ID
workspaceIdYesExact ID returned by a Company tool; never a personal platformId
approvalStatusNoFilter by the current client approval state, independently of publishing status
includeApprovalNoOpt in to client approval fields; omitted by default for compatibility

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / approvalStatus / enum
      Previous value: -[
      -  "none",
      -  "pending",
      -  "approved",
      -  "changes_requested",
      -  "outdated"
      -]New value: +[
      +  "none",
      +  "pending",
      +  "approved",
      +  "declined",
      +  "changes_requested",
      +  "outdated"
      +]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the baseline burden is low, and the description still adds value: it pins the date range to UTC, warns that filters must stay constant across cursor pages, and explains that includeApproval is an opt-in defaulted off for compatibility. It omits return shape and ordering, which keeps it below 5.

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?

Three short sentences, front-loaded with the core read operation, then filters, then pagination, then the opt-in flag. Dense and efficient; only the approval clauses are slightly compressed to the point of terseness.

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 9-parameter read tool with no output schema, the description covers filtering and pagination well but says nothing about what a calendar entry contains, ordering, or the limit default, so an agent cannot anticipate the response. Adequate rather than complete.

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 78%, so the baseline is 3; the description earns above that by clarifying the statuses filter spans both publishing and approval state, pinning 'nextCursor' to the cursor param, naming channelKey as a filter, and explaining what includeApproval unlocks. It still doesn't touch limit or the required from/to beyond the UTC note.

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?

Opens with a specific verb and resource ('Read the Agency Workspace calendar') plus a scoping constraint ('within a UTC date range'), which is far better than the tautological title. It does not explicitly distinguish itself from the closely related company_list_posts sibling, so it stops short of a 5.

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?

Provides real operational guidance for pagination ('follow nextCursor with unchanged filters') and states the optional filters are optional. However, it never says when to prefer this over company_list_posts or company_get_post, nor any exclusion or precondition beyond the implicit need for a workspaceId.

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.