Skip to main content
Glama

get_community_resources

Access Backstage community resources including support channels, plugins, FAQs, learning materials, adoption stories, and contribution guidelines to enhance your development experience.

Instructions

Get community resources, support channels, and common questions about Backstage

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoSpecific category to retrieve (optional)

Implementation Reference

  • The handler function that executes the tool logic. It retrieves the community resources content for the given category (or all if unspecified) from the knowledge base and returns it as a formatted JSON text response in the MCP content format.
    private getCommunityResources(category?: string) {
      const content = category ? 
        this.knowledgeBase.community.content[category] : 
        this.knowledgeBase.community.content;
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(content, null, 2),
          },
        ],
      };
    }
  • The input schema defining the optional 'category' parameter with allowed enum values for filtering community resources.
    inputSchema: {
      type: 'object',
      properties: {
        category: {
          type: 'string',
          description: 'Specific category to retrieve (optional)',
          enum: ['officialChannels', 'communityPlugins', 'commonQuestions', 'learningResources', 'adoptionStories', 'contributing']
        }
      }
    }
  • src/index.ts:93-105 (registration)
    Registration of the tool in the ListTools response, including name, description, and input schema.
      name: 'get_community_resources',
      description: 'Get community resources, support channels, and common questions about Backstage',
      inputSchema: {
        type: 'object',
        properties: {
          category: {
            type: 'string',
            description: 'Specific category to retrieve (optional)',
            enum: ['officialChannels', 'communityPlugins', 'commonQuestions', 'learningResources', 'adoptionStories', 'contributing']
          }
        }
      }
    },
  • src/index.ts:183-184 (registration)
    Dispatch/registration in the CallToolRequest switch statement that routes to the handler method.
    case 'get_community_resources':
      return this.getCommunityResources(args?.category as string);
  • Supporting data file providing the structured community resources content used by the handler.
    export const communityResources = {
      title: "Backstage Community Resources",
      description: "Community resources, common questions, and support channels",
      content: {
        officialChannels: {
          discord: {
            url: "https://discord.gg/backstage-687207715902193673",
            description: "Main community Discord server for support and discussions",
            channels: [
              "#general - General discussions",
              "#help - Get help with Backstage",
              "#plugin-development - Plugin development discussions",
              "#showcase - Show off your Backstage implementations",
              "#contributors - For contributors and maintainers"
            ]
          },
          github: {
            main: "https://github.com/backstage/backstage",
            community: "https://github.com/backstage/community",
            communityPlugins: "https://github.com/backstage/community-plugins"
          },
          documentation: "https://backstage.io/docs",
          blog: "https://backstage.io/blog",
          newsletter: "https://info.backstage.spotify.com/newsletter"
        },
        communityPlugins: {
          registry: "https://github.com/backstage/community-plugins",
          popular: [
            "kubernetes - Kubernetes cluster integration",
            "jenkins - Jenkins CI/CD integration", 
            "sonarqube - Code quality metrics",
            "grafana - Monitoring dashboards",
            "jira - Issue tracking integration",
            "github-actions - GitHub Actions integration",
            "datadog - Monitoring and observability",
            "newrelic - Application performance monitoring"
          ]
        },
        commonQuestions: {
          gettingStarted: [
            "How do I create my first Backstage app?",
            "What are the system requirements for Backstage?",
            "How do I configure authentication?",
            "How do I add entities to the catalog?"
          ],
          pluginDevelopment: [
            "How do I create a custom plugin?",
            "How do I integrate with external APIs?",
            "How do I add custom entity types?",
            "How do I create scaffolder actions?",
            "How do I add custom pages to Backstage?"
          ],
          deployment: [
            "How do I deploy Backstage to production?",
            "What database should I use?",
            "How do I configure HTTPS?",
            "How do I set up monitoring?",
            "How do I backup my Backstage instance?"
          ],
          troubleshooting: [
            "Plugin not loading correctly",
            "Authentication issues",
            "Database connection problems",
            "Build and deployment errors",
            "Performance optimization"
          ]
        },
        learningResources: {
          tutorials: [
            "Getting Started with Backstage",
            "Building Your First Plugin",
            "Integrating External Services",
            "Customizing the Software Catalog",
            "Setting up TechDocs"
          ],
          videos: [
            "KubeCon presentations on Backstage",
            "Spotify engineering blog videos",
            "Community meetup recordings"
          ],
          workshops: [
            "Backstage Community Sessions (monthly)",
            "Plugin development workshops",
            "Deployment and operations training"
          ]
        },
        adoptionStories: {
          companies: [
            "Spotify - Original creator and heavy user",
            "Netflix - Large-scale deployment",
            "Expedia - Multi-team adoption",
            "American Airlines - Enterprise implementation",
            "IKEA - Retail industry use case"
          ],
          useCases: [
            "Developer portal consolidation",
            "Service catalog management", 
            "Documentation centralization",
            "Scaffolding standardization",
            "Infrastructure visibility"
          ]
        },
        contributing: {
          ways: [
            "Code contributions to core",
            "Plugin development",
            "Documentation improvements",
            "Bug reports and feature requests",
            "Community support"
          ],
          governance: "CNCF governance model with technical steering committee",
          codeOfConduct: "Contributor Covenant Code of Conduct"
        }
      }
    };
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 only states what the tool does ('Get') without detailing aspects like whether it's read-only, requires authentication, has rate limits, or what the output format might be. This is a significant gap for a tool with no structured behavioral hints.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized, making it easy to parse quickly, with every part contributing essential 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 lack of annotations and output schema, the description is incomplete. It doesn't address behavioral traits, output details, or usage context, which are crucial for an agent to effectively invoke this tool. The schema covers parameters well, but overall context is insufficient for a tool with no other structured guidance.

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?

The input schema has 100% description coverage, with a well-documented optional 'category' parameter including an enum. The description doesn't add any parameter-specific information beyond what the schema provides, such as examples or usage tips, but the schema's completeness justifies the baseline score of 3.

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 tool's purpose with specific verbs ('Get') and resources ('community resources, support channels, and common questions about Backstage'), making it easy to understand what it retrieves. However, it doesn't explicitly differentiate from sibling tools like 'search_backstage_knowledge' or 'get_backstage_overview', which might have overlapping scopes.

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 any prerequisites, exclusions, or comparisons to sibling tools such as 'search_backstage_knowledge' for more specific queries or 'get_backstage_overview' for general information, leaving the agent without usage context.

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

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/PawelWaj/MCP'

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