Skip to main content
Glama

get_theming_guide

Retrieve the PrimeNG theming guide to customize themes, apply dark mode, and personalize UI components for Angular applications.

Instructions

Obtiene la guía de theming de PrimeNG (temas, personalización, modo oscuro)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler logic for executing the get_theming_guide tool: checks cache, scrapes the 'theming' guide using DocsScraperService, caches result, formats with formatGuideDoc, and returns response.
    async execute(_args: Record<string, any>): Promise<ToolResponse> {
      try {
        // Check cache first
        const cachedGuide = await this.cacheService.getGuide(this.guideName);
        if (cachedGuide) {
          logger.info(`Returning cached guide: ${this.guideName}`);
          return this.createResponse(formatGuideDoc(cachedGuide));
        }
    
        // Scrape guide
        const guide = await this.scraperService.scrapeGuide(this.guideName);
    
        // Cache the result
        await this.cacheService.setGuide(this.guideName, guide);
    
        return this.createResponse(formatGuideDoc(guide));
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return this.createErrorResponse(
          `Failed to get ${this.guideName} guide: ${errorMessage}`
        );
      }
    }
  • Specific tool handler class for 'get_theming_guide', extends GetGuideTool and configures it for the 'theming' guide section.
    export class GetThemingGuideTool extends GetGuideTool {
      constructor(scraperService: DocsScraperService, cacheService: CacheService) {
        super('get_theming_guide', 'theming', scraperService, cacheService);
      }
  • Input schema definition for the get_theming_guide tool (no input params required).
    /**
     * Creates the schema for get_theming_guide tool
     */
    export function createGetThemingGuideSchema(): Tool {
      return {
        name: "get_theming_guide",
        description: "Obtiene la guía de theming de PrimeNG (temas, personalización, modo oscuro)",
        inputSchema: {
          type: "object",
          properties: {},
        },
      };
    }
  • Tool dispatch/registration in server request handler: calls getThemingGuideTool.run() for 'get_theming_guide'.
    case "get_theming_guide":
      return await this.getThemingGuideTool.run(args);
  • Instantiation/registration of GetThemingGuideTool instance in PrimeNGServer.
    this.getThemingGuideTool = new GetThemingGuideTool(
      this.docsScraperService,
      this.cacheService
    );
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 a theming guide but doesn't describe what the return format looks like (e.g., text, structured data), whether it's cached, if there are rate limits, or any authentication needs. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 includes relevant details (temas, personalización, modo oscuro) without unnecessary elaboration. However, it could be slightly more structured by explicitly separating the purpose from the content scope.

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 has 0 parameters, no annotations, and no output schema, the description is minimally adequate. It states what the tool does but lacks details on behavioral traits, return format, or usage context. For a simple retrieval tool, this might suffice, but it doesn't fully compensate for the lack of structured data, leaving gaps in understanding how to use it effectively.

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 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. Baseline 4 is applied for zero-parameter tools, as no compensation is needed.

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 a specific verb ('Obtiene') and resource ('guía de theming de PrimeNG'), including what content it covers (temas, personalización, modo oscuro). It distinguishes itself from siblings like get_installation_guide or get_tailwind_guide by focusing on theming. However, it doesn't explicitly differentiate from all siblings (e.g., get_icons_guide is also a guide-type tool).

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 compare it to siblings like get_component_doc or search_components for related information. Usage is implied by the purpose but not explicitly stated.

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/hnkatze/PrimeNG_MCP'

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