Skip to main content
Glama

get_anti_patterns

Identify known bottlenecks, root causes, and fixes. Read this before patching inline to avoid common issues.

Instructions

Returns the full list of known bottlenecks, their root causes, and fixes. Read this when something looks wrong before patching inline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • api/mcp.ts:603-606 (registration)
    Registers the 'get_anti_patterns' tool with the MCP server. No input parameters required. Returns the ANTI_PATTERNS constant.
    /* 7. get_anti_patterns */
    server.tool("get_anti_patterns", "Known bottlenecks and fixes.", {}, async () => {
      return { content: [{ type: "text" as const, text: ANTI_PATTERNS }] };
    });
  • Static data constant containing the markdown table of anti-patterns (8 known bottlenecks with symptoms, root causes, and fixes). This is the data payload returned by the tool.
    const ANTI_PATTERNS = `# Known Bottlenecks & Anti-Patterns\n\n| # | Symptom | Root cause | Fix |\n|---|---|---|---|\n| 1 | Reports quicklink plain text | line-tab.css not linked | Add line-tab.css link |\n| 2 | ActionBar has view-toggle on Reports | Using Type 1-7 | Reports = Type 8 |\n| 3 | Table columns uneven | Hard-coded col widths | Checkbox=32px, rest=no width |\n| 4 | Drawer body flush | style="padding:0" | Use --no-pad modifier |\n| 5 | classic-tab in drawer | Used classic-tab inside drawer | Use line-tab inside drawers |\n| 6 | Tabs switch but no change | Custom data-*-tab attributes | Use standard data-tab only |\n| 7 | Dropdown 432px in drawer | flex:1 override | Delete override, use 280px fixed |\n| 8 | table-scroll-area gone | Missing min-height:0 | Every ancestor: flex:1; min-height:0; overflow:hidden |`;
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that the tool is read-only ('Returns...') but adds no details about potential side effects, performance, or size. For a simple list retrieval, this is adequate but minimal, scoring a 3.

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?

Two sentences: first defines the function, second gives usage guidance. No extraneous words, front-loaded with the primary action. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and simple inputs, the description adequately covers what the tool returns (bottlenecks, root causes, fixes) and when to use it (before patching). It lacks details on output format or pagination, but for a diagnostic list tool this is largely sufficient, so a 4.

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 input schema has zero parameters with 100% coverage. Per guidelines, zero parameters baseline is 4. The description adds the meaning of returning a 'full list', which is consistent but does not provide additional syntax or format details beyond the schema's emptiness.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns a 'full list of known bottlenecks, their root causes, and fixes'. It uses a specific verb ('returns') and describes the resource comprehensively, distinguishing it from sibling tools like 'get_chart_snippet' or 'get_checklist' which focus on different content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description instructs 'Read this when something looks wrong before patching inline', providing a clear usage scenario. It implies an alternative (patching inline) and gives context for when to use this diagnostic tool, though it does not explicitly name a sibling for exclusion.

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/Anguraj-zoho/elegant-mcp'

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