Skip to main content
Glama
brianellin

Bluesky MCP Server

by brianellin

list-resources

Discover and access all MCP resources available on the Bluesky MCP Server, including descriptions, to optimize AI assistant interactions with Bluesky/ATProtocol features.

Instructions

List all available MCP resources with their descriptions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:1438-1453 (registration)
    Registration of the 'list-resources' tool including inline handler that formats and returns the list of available MCP resources using the imported resourcesList
    server.tool(
      "list-resources",
      "List all available MCP resources with their descriptions",
      {},
      async () => {
        const formattedResources = resourcesList.map((resource, index) => {
          return `Resource #${index + 1}:
    Name: ${resource.name}
    URI: ${resource.uri}
    Description: ${resource.description}
    ---`;
        }).join("\n\n");
    
        return mcpSuccessResponse(`Available MCP Resources:\n\n${formattedResources}\n\nTo use these resources, reference them by URI in your prompts or queries.`);
      }
    );
  • Array containing metadata of available MCP resources, used by the list-resources tool handler to generate the response
    export const resourcesList = [
      {
        name: "bluesky-platform-info",
        uri: "bluesky://platform-info",
        description: "Comprehensive information about the Bluesky platform, its features, and culture"
      },
      {
        name: "bluesky-post-schema",
        uri: "bluesky://post-schema",
        description: "Technical documentation of the Bluesky post schema and structure"
      }
    ]; 
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't describe behavioral traits such as whether it's read-only, if it requires authentication, rate limits, pagination, or what the output format looks like (e.g., list structure, error handling). This is a significant gap for a tool with no annotation coverage.

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 description is a single, clear sentence that efficiently conveys the core purpose without any wasted words. It's front-loaded and appropriately sized for a simple tool, making it easy for an agent to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what 'MCP resources' entail (e.g., types, scope), how results are returned, or any limitations. For a tool that presumably returns a list of resources, more context on output behavior is needed to be fully helpful to an agent.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is applied as it adequately handles the lack of parameters without introducing confusion.

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?

The description clearly states the verb ('List') and resource ('all available MCP resources with their descriptions'), making the purpose specific and understandable. It doesn't explicitly differentiate from sibling tools, but since it's the only tool that lists MCP resources (others focus on posts, profiles, feeds, etc.), the distinction is implicit rather than explicit.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for usage, or comparisons to sibling tools like 'search-feeds' or 'search-posts' that might serve similar discovery purposes. This leaves the agent without explicit usage instructions.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/brianellin/bsky-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server