Skip to main content
Glama
miniOrangeDev

WordPress Code Review MCP Server

get_guidelines

Retrieve coding guidelines, security rules, and validation patterns from external sources to maintain code quality standards in WordPress projects.

Instructions

Get development guidelines from the configured source

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoOptional category of guidelines to retrieve (e.g., security-rules, validation-rules)

Implementation Reference

  • The core handler function that executes the get_guidelines tool logic: fetches guidelines from the source using the provided category and returns formatted text content.
    private async getGuidelines(category?: string) {
      try {
        const content = await this.guidelineSource.fetchGuidelines(category);
        
        return {
          content: [
            {
              type: 'text',
              text: content,
            },
          ],
        };
      } catch (error) {
        throw new Error(`Failed to fetch guidelines: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
  • Defines the input schema and metadata for the get_guidelines tool, including optional 'category' parameter.
    {
      name: 'get_guidelines',
      description: 'Get development guidelines from the configured source',
      inputSchema: {
        type: 'object',
        properties: {
          category: {
            type: 'string',
            description: 'Optional category of guidelines to retrieve (e.g., security-rules, validation-rules)',
          },
        },
      },
    },
  • src/index.ts:48-52 (registration)
    Registers the handler for listing tools, which includes the get_guidelines tool definition and schema.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: guidelinesManager.getTools(),
      };
    });
  • src/index.ts:54-57 (registration)
    Registers the generic tool call handler that dispatches get_guidelines calls to GuidelinesManager.handleTool.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
      return await guidelinesManager.handleTool(name, args);
    });
  • Dispatch case in handleTool method that routes get_guidelines calls to the specific handler.
    case 'get_guidelines':
      return await this.getGuidelines(args.category);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Get' which implies a read operation, but doesn't cover aspects like authentication needs, rate limits, error handling, or what 'configured source' entails. This leaves significant gaps for a tool with no annotation support.

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 with zero waste, clearly front-loading the core action. It's appropriately sized for a simple retrieval tool, earning full marks for conciseness.

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 no annotations, no output schema, and a simple input schema, the description is incomplete. It lacks details on behavioral traits, usage context, and what 'configured source' means, making it inadequate for guiding an AI agent effectively beyond basic purpose.

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 the parameter 'category' documented as optional and including examples. The description doesn't add any meaning beyond this, as it doesn't mention parameters at all. Baseline 3 is appropriate when 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 verb 'Get' and resource 'development guidelines from the configured source', making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'security_check' or 'validate_code', which might also relate to guidelines or rules, so it doesn't reach the highest 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?

No guidance is provided on when to use this tool versus alternatives like the sibling tools 'security_check' or 'validate_code'. The description implies retrieval but doesn't specify contexts, prerequisites, or exclusions, leaving usage ambiguous.

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/miniOrangeDev/wp-code-review-mcp-server'

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