Skip to main content
Glama

Set resource

set_resource
Destructive

Add a room or a unit of equipment to a project's resources, or change the one named by 'id' — the WHOLE of it as written. Without 'id', an 'externalId' the project has changes that resource. Its buffers are minutes before and after an event during which it is still busy (setting up, clearing). Setting 'status' to 'repair' keeps it on the events that have it — they then show a conflict — and refuses it to new ones. Conflicts that appear or clear are told to webhooks of 'calendar:resource_conflict'. Anybody who may write in the project.

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": {
      "project": "<project>",
      "name": "<name>"
    },
    "name": "set_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoWhere it stands on the plan, millimetres.
yNoWhere it stands on the plan, millimetres.
idNoThe resource to change. Leave out to add one.
kindNo'room' or 'equipment' (default).
nameYesIts name, e.g. 'Hall' or 'Big Dipper #3'.
noteNoFree text.
statusNo'available' (default) or 'repair'.
projectYesThe project key, e.g. TH.
externalIdNoYour own id for it, unique in the project.
bufferAfterNoMinutes after an event it is busy (clearing), 0-1440.
moveMinutesNoMinutes it takes to move or hang it at another point, 0-1440 — what a reconfiguration moving it lasts. Leave out to keep (15 for a new one).
bufferBeforeNoMinutes before an event it is busy (setting up), 0-1440.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / moveMinutes
      Added value: +{
      +  "default": null,
      +  "description": "Minutes it takes to move or hang it at another point, 0-1440 — what a reconfiguration moving it lasts. Leave out to keep (15 for a new one).",
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say destructiveHint=true and readOnlyHint=false; the description earns its keep by disclosing that the change replaces "the WHOLE of it as written," that status='repair' keeps the resource on existing events (surfacing conflicts) and blocks new ones, and that conflict changes fire calendar:resource_conflict webhooks. Those side effects and the write-permission requirement are exactly the context an agent needs for a destructive mutation.

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 critical create-vs-update distinction and the full-replace warning are front-loaded, and there is no filler. The prose is telegraphic in places ("Its buffers are minutes before and after an event during which it is still busy") and the trailing permission fragment requires a second read, costing it a point.

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

Completeness4/5

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

For a 12-parameter destructive mutation with no output schema, the description covers the essentials: upsert matching, replacement semantics, conflict webhooks, repair status, and authorization. It stops short of saying what the call returns (e.g., the resource id) and leaves a mild tension between "the WHOLE of it as written" and moveMinutes' "leave out to keep," which an agent could misread as patch semantics.

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 100%, so baseline is 3, but the description adds genuine meaning for key parameters: buffers are explained as busy minutes before/after an event (setting up, clearing), status='repair' behavior is unpacked, and externalId is framed as a matching key rather than just an id. Coordinates, moveMinutes, note, and kind are left to the schema, so it is above baseline but not exhaustive.

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 opens with a precise verb+resource: "Add a room or a unit of equipment to a project's resources, or change the one named by 'id'." It explicitly distinguishes the create path (no id) from the update path (id, or matching externalId), so an agent can tell which mode it is invoking before touching the schema.

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?

It spells out the conditions that select each mode: omit 'id' to add, supply 'id' to change, or supply an 'externalId' the project already has to change that resource. Permission scope is stated ("Anybody who may write in the project"). It does not name the delete_resource alternative or state when not to use this tool, which keeps it short of a 5.

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.

Resources