Skip to main content
Glama
Sign In
Deferno MCP Server

Deferno MCP Server

by Circuit-Stitch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

patch_event_occurrence_comment

Edit the latest comment on an event occurrence using event ID and date. Optional fields allow changing body or privacy.

Instructions

Edit the latest comment on an event occurrence (date).

event_id accepts any reference form — UUID, sequence shorthand (#123, personal-org only), canonical ref (acme-123), or app URL — and is resolved to a UUID before the edit.

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": {
      "event_id": "<event_id>",
      "date": "<date>"
    },
    "name": "patch_event_occurrence_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYes
dateYes
bodyNo
is_privateNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

The description discloses the important behavior of event_id resolution (accepts various reference forms, resolves to UUID). However, with no annotations, other behaviors (e.g., what happens if no comment exists, idempotency, permissions) are not covered.

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 concise with two sentences, front-loading the core purpose and providing key parameter detail without fluff.

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?

An output schema exists, which may cover return values, but the description omits details on parameter behaviors, effect of optional fields, and any prerequisites. Given the tool's complexity (4 params, no annotations), the description is moderately incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only the event_id parameter is explained in detail. The other three parameters (date, body, is_private) are not described beyond their schema types, and schema description coverage is 0%. The description does not compensate for the lack of schema documentation.

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 clearly states 'Edit the latest comment on an event occurrence (date)', specifying the verb and resource. However, it does not explicitly distinguish this tool from siblings like 'post_event_occurrence_comment' or 'update_comment'.

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 is provided on when to use this tool versus alternatives such as 'post_event_occurrence_comment' or 'delete_event_occurrence_comment'. The description lacks any conditions or exclusions.

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