Skip to main content
Glama

update_grid_placeholder

Idempotent

Change a placeholder's time slot, note or colour. Omit what you don't want to change; note="" really clears the note. Same rules as create_grid_placeholder (timezone-aware slot_at, note up to 280 characters, a palette colour).

Colours: #84fab0, #a1c4fd, #c3cfe2, #d4fc79, #e0c3fc, #f6d365, #fbc2eb, #fdcbf1, #ff9a9e (default #f6d365).

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": {
      "workspace_id": "<workspace_id>",
      "placeholder_id": "<placeholder_id>"
    },
    "name": "update_grid_placeholder"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
colorNo
slot_atNo
workspace_idYes
placeholder_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
noteYes
colorYes
slot_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare a non-destructive, idempotent mutation, so the bar is lower; the description still adds genuinely non-obvious behavior: omitted fields are left untouched and note="" is the explicit way to clear a note. It also discloses the 280-character note cap and that slot_at is timezone-aware, details the annotations cannot convey. It does not mention what a successful response contains, though an output schema covers that.

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?

Front-loaded with the action and the omit-to-keep rule first, then the shared validation rules. The palette list takes a full line but is payload rather than padding, since the schema has no enum for color.

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 5-parameter mutation with an output schema present, the description covers mutation semantics, clearing behavior, validation limits, and allowed colour values. Return values need not be explained and annotations handle the safety profile, leaving only the two identifier parameters implicit.

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 description coverage is 0% across 5 parameters, so the description must carry the load and largely does: note (max 280 chars, empty string clears), color (explicit palette with a stated default of #f6d365), and slot_at (timezone-aware date-time). Only workspace_id and placeholder_id are left unexplained, which is a minor gap for self-evident identifiers.

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?

States a specific verb ('Change') and resource ('a placeholder'), and enumerates exactly which attributes are mutable: time slot, note, colour. The verb cleanly separates it from siblings named create_grid_placeholder and delete_grid_placeholder without needing their schemas.

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?

'Omit what you don't want to change' gives clear partial-update semantics, and 'Same rules as create_grid_placeholder' routes the agent to the sibling that documents validation. It stops short of explicit when-not-to-use guidance (e.g. use convert_grid_placeholder to move an entry), but the usage context is unambiguous.

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