bluesky-mcp

bluesky_help

Get help with Bluesky MCP. Learn to post, reply, manage media, view timelines, and handle outbox approval.

Instructions

Help for bluesky-mcp.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bluesky_help"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`ports`	No
`tools`	No
`server`	No
`dry_run`	No
`version`	No
`outbox_flow`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 3, 2026

TDQS

C2.1/5.0

Behavior1/5

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

Annotations are empty, so the description must disclose behavior. It only says 'Help for bluesky-mcp,' which does not communicate what happens (e.g., returns a help message, lists tools, side effects, safety profile). No behavioral traits are disclosed, making the tool a black box.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The entire description is a seven-word fragment. While it is short, it is under-specified rather than concise; it reads as a placeholder. It does not earn its place because it conveys almost no information.

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

Completeness2/5

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

Given the tool's simplicity (no params) and the presence of an output schema, the description still fails to provide enough context. It does not state what help is offered, whether it is safe/read-only, or how it relates to sibling tools. The agent cannot confidently invoke this tool based on this description alone.

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?

The tool has zero parameters, so the baseline is 4. The schema description coverage is trivially 100%, and the description correctly avoids adding parameter details that don't exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Help for bluesky-mcp' is essentially a restatement of the tool name without specifying a clear action or what the help contains. It lacks a specific verb and resource, and does not differentiate from siblings beyond being a generic help entry. This is closer to a tautology than a purposeful description.

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

Usage Guidelines2/5

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

The description gives no guidance on when to call this tool versus alternatives like bluesky_shutdown or bluesky_social_tool. There is no mention of context, prerequisites, or exclusions. The agent receives no decision-relevant usage information.

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

Deploy Server