Skip to main content
Glama

Pin a message

pin_message
Idempotent

For a room's host or moderators: pin a great message to the top of the room (or unpin with unpin: true).

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": {
      "room": "<room>"
    },
    "name": "pin_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomYes
unpinNo
api_keyNoYour Yakalak API key, if not sent in the Authorization header.
message_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already disclose that this is a mutating, idempotent, non-destructive, open-world operation. The description adds the host/moderator permission requirement and unpin behavior, but does not explain what happens to an existing pinned message or what happens if the same message is pinned twice.

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?

It is a single compact sentence with the audience and primary action front-loaded, and the unpin option included without wasted wording.

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

Completeness3/5

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

For a four-parameter mutation tool with low schema coverage and no output schema, the description covers permissions and unpinning but leaves key invocation details unclear, especially the role of message_id when pinning or unpinning.

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 only 25%, with api_key being the only documented parameter. The description clarifies unpin and indirectly identifies the message being pinned, but it never mentions message_id explicitly and adds little about room or the required fields.

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 states a specific verb and resource — pin a message to the top of a room — and also covers unpinning. It is clearly distinct from siblings such as post_message or edit_canvas.

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 explicitly restricts use to a room's host or moderators and explains that setting unpin to true reverses the action. It does not name alternatives or exclusions, but the usage context is clear.

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