Skip to main content
Glama

get_backstage_overview

Retrieve comprehensive Backstage framework overview including core features, benefits, and architecture to understand platform capabilities and implementation.

Instructions

Get comprehensive overview of Backstage framework including core features, benefits, and architecture

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionNoSpecific section to retrieve (optional)

Implementation Reference

  • The core handler function for the 'get_backstage_overview' tool. Retrieves content from the backstageOverview knowledge base, optionally filtered by section, and returns it as JSON-formatted text.
    private getBackstageOverview(section?: string) {
      const content = section ? 
        this.knowledgeBase.overview.content[section] : 
        this.knowledgeBase.overview.content;
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(content, null, 2),
          },
        ],
      };
    }
  • src/index.ts:50-63 (registration)
    Tool registration in ListToolsRequestSchema response, defining name, description, and input schema.
    {
      name: 'get_backstage_overview',
      description: 'Get comprehensive overview of Backstage framework including core features, benefits, and architecture',
      inputSchema: {
        type: 'object',
        properties: {
          section: {
            type: 'string',
            description: 'Specific section to retrieve (optional)',
            enum: ['whatIsBackstage', 'coreFeatures', 'benefits', 'architecture']
          }
        }
      }
    },
  • Supporting data structure providing the actual content for the backstage overview tool, structured by sections.
    export const backstageOverview = {
      title: "Backstage Overview",
      description: "Comprehensive overview of Backstage framework",
      content: {
        whatIsBackstage: {
          definition: "Backstage is an open source framework for building developer portals. Powered by a centralized software catalog, Backstage restores order to your microservices and infrastructure and enables your product teams to ship high-quality code quickly — without compromising autonomy.",
          purpose: "Backstage unifies all your infrastructure tooling, services, and documentation to create a streamlined development environment from end to end.",
          cncfStatus: "CNCF Incubation project after graduating from Sandbox"
        },
        coreFeatures: {
          softwareCatalog: {
            name: "Backstage Software Catalog",
            description: "For managing all your software (microservices, libraries, data pipelines, websites, ML models, etc.)",
            useCase: "Central registry of all software components in your organization"
          },
          softwareTemplates: {
            name: "Backstage Software Templates",
            description: "For quickly spinning up new projects and standardizing your tooling with your organization's best practices",
            useCase: "Scaffolding new services with organizational standards"
          },
          techDocs: {
            name: "Backstage TechDocs",
            description: "For making it easy to create, maintain, find, and use technical documentation, using a 'docs like code' approach",
            useCase: "Documentation as code integrated with your software catalog"
          },
          plugins: {
            name: "Plugin Ecosystem",
            description: "Growing ecosystem of open source plugins that further expand Backstage's customizability and functionality",
            useCase: "Extensible platform for custom integrations"
          }
        },
        benefits: {
          engineeringManagers: "Maintain standards and best practices across the organization, manage whole tech ecosystem from migrations to test certification",
          developers: "Fast and simple to build software components in a standardized way, central place to manage all projects and documentation",
          platformEngineers: "Extensibility and scalability by easily integrating new tools and services via plugins",
          everyone: "Single, consistent experience that ties all infrastructure tooling, resources, standards, owners, contributors, and administrators together"
        },
        architecture: {
          frontend: "React-based frontend application",
          backend: "Node.js backend with plugin architecture",
          database: "PostgreSQL for persistent storage",
          plugins: "Microservice-like plugin architecture for extensibility"
        }
      }
    };
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 the tool retrieves an overview but doesn't cover aspects like whether it's read-only, requires authentication, has rate limits, or what the return format is. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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

Conciseness4/5

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

The description is a single, efficient sentence that front-loads the core purpose. It avoids unnecessary words and directly states what the tool does. However, it could be slightly more structured by explicitly mentioning the optional parameter or output details, though this is minor.

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?

Given the tool's low complexity (one optional parameter, no output schema, no annotations), the description is minimally adequate. It covers the purpose but lacks details on behavior, usage context, and output format. For a simple read operation, this is acceptable but not comprehensive, aligning with a baseline score.

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 one optional parameter 'section' fully documented via enum values. The description adds no additional parameter semantics beyond what the schema provides, such as default behavior if no section is specified. Baseline 3 is appropriate since the schema does the heavy lifting.

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: 'Get comprehensive overview of Backstage framework including core features, benefits, and architecture.' It specifies the verb ('Get') and resource ('overview of Backstage framework') with scope details. However, it doesn't explicitly differentiate from sibling tools like 'get_api_reference' or 'search_backstage_knowledge,' which prevents a perfect score.

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 sibling tools like 'get_backstage_examples' or 'search_backstage_knowledge,' nor does it specify prerequisites or exclusions. Usage is implied by the purpose but lacks explicit context for selection.

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