Skip to main content
Glama

remove_grid_collab

DestructiveIdempotent

Take a Collab tile off the grid (the id is its grid tile id from get_grid). It only removes reeldrop's tile — the post on Instagram is untouched.

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>",
      "collab_id": "<collab_id>"
    },
    "name": "remove_grid_collab"
  }
}

Input Schema

NameRequiredDescriptionDefault
collab_idYes
workspace_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds the crucial scope detail that only the grid tile is removed and the underlying Instagram post survives — exactly the consequence an agent needs before a destructive call. It does not say whether the removal is reversible or whether remaining tiles reflow.

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?

Two sentences, no filler, with the operation and its scope stated first and the important non-effect clarification second. Every clause carries information an agent needs.

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?

An output schema exists, so return values need not be described, and the core destructive-scope question is answered. Minor gaps remain: no explanation of workspace_id and no note on whether grid layout shifts after removal.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema documents neither of the two parameters. The description compensates for collab_id by explaining it is the grid tile id obtained from get_grid, but says nothing about workspace_id, leaving half the parameter semantics unexplained.

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 ("Take a Collab tile off the grid") and explicitly scopes the effect to reeldrop's tile, noting the Instagram post is untouched. This separates it from a post-level deletion, but it does not explicitly contrast with grid-mutating siblings like swap_grid_entries or add_grid_collab.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the operation itself, and the description usefully clarifies what is NOT affected (the Instagram post), which is the main ambiguity an agent would have. There is no explicit when-to-use versus when-not guidance or named alternative for other kinds of grid removal.

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