Skip to main content
Glama
Sign In
飞书日历 MCP 服务器

飞书日历 MCP 服务器

by xiuxiuxius
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

feishu_subscribe_calendar

Subscribe to a Feishu calendar by calendar ID to add it to your calendar list and receive its event updates.

Instructions

订阅日历 (Subscribe to calendar)

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": {
      "calendar_id": "<calendar_id>"
    },
    "name": "feishu_subscribe_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
calendar_idYes日历 ID (Calendar ID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.2

TDQS

C2.1/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing beyond the bare verb. It does not state whether the operation is idempotent, what happens if the calendar is already subscribed, what permissions are required, or what side effects occur.

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?

It is a single short bilingual phrase with no wasted words, but the brevity reflects under-specification rather than tight editing. There is no structure to speak of because there is no substantive content.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation-like tool with no annotations and no output schema, the description should carry the safety and behavior profile; instead it offers only the name restated. The only element that is complete (the parameter list) is already covered by the schema.

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?

There is a single required parameter with 100% schema description coverage, so the schema already documents calendar_id. The description adds no syntax, format, or sourcing detail beyond the schema, which is the expected baseline when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a direct bilingual restatement of the tool name ('订阅日历 / Subscribe to calendar') with no added specificity. It tells the agent nothing the identifier did not already convey and does not distinguish it from its closest sibling, feishu_unsubscribe_calendar.

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

Usage Guidelines2/5

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

No guidance on when to subscribe, what precondition must hold (e.g. an existing calendar the caller can access), or how this relates to feishu_get_calendar_list / feishu_unsubscribe_calendar. The agent must infer usage from the name alone.

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

Deploy Server

Other Tools