Skip to main content
Glama
Sign In
Revel Digital MCP Server

Revel Digital MCP Server

Official
by RevelDigital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

patchschedule

Apply partial updates to a schedule using the JSON Patch syntax. Target specific properties without replacing the entire schedule.

Instructions

Patch a schedule. Patch allows partial updates by targeting specific properties of the schedule. Uses the JSON Patch syntax (http://jsonpatch.com)

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": {
      "id": "<id>"
    },
    "name": "patchschedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSchedule Id
requestBodyNoPatch update

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.20

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions JSON Patch syntax but does not disclose side effects, permissions, idempotency, or error handling.

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 very concise with three short sentences, front-loading the main purpose. Every sentence adds value without redundancy.

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?

The tool has no output schema and only two parameters. The description covers the basic behavior but lacks details on return values, error cases, or handling of invalid patches.

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?

The description adds meaning by specifying that requestBody uses JSON Patch syntax, which goes beyond the schema's simple 'Patch update' description. This helps the agent understand the required format.

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 'Patch a schedule' with the specific verb 'patch' and resource 'schedule'. It emphasizes partial updates, distinguishing it from full update tools like putschedule.

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 explains that patch allows partial updates, which indicates when to use it (for partial updates) but does not explicitly mention when not to use it or name alternative tools.

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