Skip to main content
Glama
Sign In
@nexalware/mcp

@nexalware/mcp

Official
by nexalware
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

update_schedule

Modify an existing device schedule slot, changing only the fields you provide.

Instructions

Update an existing schedule slot, only the fields provided are changed.

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": {
      "deviceId": "<deviceId>",
      "slot": "<slot>"
    },
    "name": "update_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
onTsNo
slotYesWhich schedule slot (0-4) to update.
labelNo
offTsNo
enabledNo
deviceIdYesThe device's public id, e.g. dev_a1b2c3.
onCommandNo
offCommandNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose a meaningful trait – partial/patch semantics, since only provided fields are changed – but omits permission requirements, error behavior for invalid slots, and whether omitted fields are truly preserved versus reset.

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?

A single tight sentence with the key constraint (partial update) front-loaded and no filler. It is appropriately sized, though the brevity leaves no room for the guidance the tool needs.

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 tool with no annotations, no output schema, nested objects, and 8 parameters at 25% coverage, the description is too thin. It should cover permissions, the meaning of slot range, the on/off command pairing, and error conditions.

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?

Schema description coverage is only 25% across 8 parameters, so the description needs to compensate but does not mention any parameter at all. The schema documents slot, deviceId, and command name, leaving onTs, offTs, label, enabled, and params undocumented in both places.

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?

States a specific verb and resource (update an existing schedule slot) and clarifies scope. It does not explicitly differentiate from create_schedule or delete_schedule, but the verb makes the distinction reasonably clear.

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?

The description gives no guidance on when to use this versus create_schedule, delete_schedule, or other schedule tools, and no prerequisites. An 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