Skip to main content
Glama
Sign In
productive-mcp-rb2

productive-mcp-rb2

by rubenlangeweg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pin_comment

pin_comment
Idempotent

Pin a comment to keep it at the top of the task discussion, ensuring important information remains visible.

Instructions

Pin a comment so it stays at the top of the task discussion.

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": {
      "comment_id": "<comment_id>"
    },
    "name": "pin_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
comment_idYesThe ID of the comment to pin

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0-alpha.7

TDQS

A4.1/5.0
Behavior4/5

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

Annotations indicate idempotent and non-destructive, but the description adds value by explaining the 'stays at top' effect, which is helpful beyond the annotation flags.

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?

Single sentence, clear, front-loaded, no wasted words or redundant information.

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

Completeness5/5

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

For a simple tool with one parameter and no output schema, the description fully explains the action and effect, leaving no gaps.

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 coverage is 100% with a single parameter comment_id, and the description does not add extra meaning beyond the schema's description, so baseline 3 is appropriate.

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 uses a specific verb 'pin' and resource 'comment', and clearly states the effect 'stays at the top of the task discussion', distinguishing it from siblings like unpin_comment.

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?

The description implies when to use (to highlight a comment) but does not explicitly mention when to avoid or alternatives like unpin_comment.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools