Skip to main content
Glama

get_tailwind_guide

Retrieve the integration guide for using Tailwind CSS with PrimeNG components in Angular applications.

Instructions

Obtiene la guía de integración de PrimeNG con Tailwind CSS

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The execute method in GetGuideTool implements the core logic for the get_tailwind_guide tool: checks cache, scrapes the 'tailwind' guide if needed, caches the result, formats it, and returns the response. This is called via run() from BaseTool.
    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}`
        );
      }
    }
  • Defines the MCP tool schema for 'get_tailwind_guide', including name, description, and empty input schema (no parameters required).
    export function createGetTailwindGuideSchema(): Tool {
      return {
        name: "get_tailwind_guide",
        description: "Obtiene la guía de integración de PrimeNG con Tailwind CSS",
        inputSchema: {
          type: "object",
          properties: {},
        },
      };
    }
  • Tool dispatch registration in the MCP CallToolRequest handler: calls getTailwindGuideTool.run() when 'get_tailwind_guide' is requested.
    case "get_tailwind_guide":
      return await this.getTailwindGuideTool.run(args);
  • Instantiation and registration of the GetTailwindGuideTool instance in PrimeNGServer during initialization.
    this.getTailwindGuideTool = new GetTailwindGuideTool(
      this.docsScraperService,
      this.cacheService
    );
  • Specific tool class for 'get_tailwind_guide' that extends GetGuideTool, configuring it with tool name and 'tailwind' guide name.
    export class GetTailwindGuideTool extends GetGuideTool {
      constructor(scraperService: DocsScraperService, cacheService: CacheService) {
        super('get_tailwind_guide', 'tailwind', scraperService, 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 'gets' a guide, implying a read-only operation, but doesn't specify whether this requires authentication, involves rate limits, returns structured or unstructured data, or has any side effects. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 in Spanish that directly states the tool's purpose without unnecessary words. It is appropriately sized for a no-parameter tool and front-loads the key action ('obtiene'). There is no wasted language or redundant information.

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 complete. It tells the agent what resource to fetch, but doesn't explain the format of the returned guide (e.g., text, HTML, JSON) or any prerequisites. For a simple read operation, this might be adequate, but it lacks depth for more complex use cases.

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 the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics beyond what the schema provides. A baseline score of 4 is appropriate as the description doesn't mislead about parameters and the schema fully covers the absence of them.

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: 'Obtiene la guía de integración de PrimeNG con Tailwind CSS' (Gets the integration guide for PrimeNG with Tailwind CSS). It specifies the verb 'obtiene' (gets) and the resource 'guía de integración' (integration guide), making the action and target clear. However, it doesn't explicitly differentiate from sibling tools like 'get_installation_guide' or 'get_theming_guide', which might also provide guides but for different topics.

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 when this specific integration guide is needed, what context it applies to, or how it differs from other guide-fetching siblings like 'get_installation_guide' or 'get_theming_guide'. Without such context, users must infer usage based on the tool name alone.

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