Skip to main content
Glama

create_grid_placeholder

Pencil an idea into the grid: a coloured tile with a short note at a time slot, no media. Nothing is scheduled or published.

slot_at is a timezone-aware ISO-8601 time (never guessed — a bare local time
is refused). note is a one-line reminder up to 280 characters ("carousel
about the new roast"), not a caption. color is one of the fixed palette
values listed below. When the idea is ready, convert_grid_placeholder turns it
into a draft post at the same slot.

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>",
      "slot_at": "<slot_at>"
    },
    "name": "create_grid_placeholder"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
colorNo#f6d365
slot_atYes
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
noteYes
colorYes
slot_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare this is a non-destructive, non-read mutation, but the description adds real behavior beyond that: nothing is scheduled or published, media is excluded, and slot_at must be timezone-aware because a bare local time is refused. It does not address duplicate creation even though idempotentHint is false, so repeating a call and getting two tiles is left unmentioned.

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 constraints sit in the first sentence, and the second sentence handles input format. The trailing palette list earns its space because the schema has no enum for color; without it, the allowed values would never appear.

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?

This is a mutating tool with an output schema, so return values need no explanation. The annotations cover the safety profile, and the description covers input formats and effects. The only remaining gaps are workspace_id semantics and what happens if the call is repeated.

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%, so the description must carry the burden of explaining the parameters, and it does for three of four: slot_at (timezone-aware ISO-8601, not guessed), note (one line, up to 280 characters, not a caption), and color (fixed palette, default #f6d365, with all values listed). Only workspace_id is left undocumented, which keeps this just short of a 5.

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?

It uses a specific verb and resource: 'Pencil an idea into the grid: a coloured tile with a short note at a time slot, no media.' It also sets this apart from convert_grid_placeholder by saying that tool turns the placeholder into a draft post, so an agent can distinguish the two without opening either 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 clearly says what this tool is not: 'Nothing is scheduled or published.' It also names the follow-on action: 'When the idea is ready, convert_grid_placeholder turns it into a draft post at the same slot.' That routing is explicit, but it does not say when to use this tool instead of creating a draft directly, and the sibling update_grid_placeholder is never mentioned.

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