Skip to main content
Glama

Naming convention check

check_naming_conventions
Read-only

Audits names. Pass names, one per line; use slashes for paths or two-space indentation for nesting. Classifies each segment as kebab, snake, camel, Pascal, upper snake, title words or lower words and reports the dominant style and strays, then flags default tool names (Frame 12, Group 4, Rectangle), draft or version markers (final, copy, new, v2), names that repeat or differ only by case or separator, stray whitespace, emoji and file-unsafe characters, names over 40 characters, depth beyond 5 levels, mixed path separators and inconsistent state casing. It flags inconsistency, not which style is right. Works on the pasted names only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "names": "<names>"
    },
    "name": "check_naming_conventions"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYesOne layer, component or token name per line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world behavior, so the bar is lower. The description adds real context beyond that: input is pasted text only (no filesystem or project traversal), the tool is opinion-neutral (flags inconsistency rather than prescribing a style), and it lists the specific violation categories it detects.

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?

Front-loaded with purpose and input format, then the flag inventory, which is dense but each item is a distinct check that helps the agent predict output. The long enumeration is justified, though a bulleted structure would be easier to scan.

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, the description carries the burden of describing results and does so in prose: dominant style, strays, and a categorized list of flags. Scope and limits (pasted names only, no style prescription) are also covered, leaving little an agent needs that is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and documents the single parameter, yet the description still adds meaningful semantics: one name per line, slashes for paths, two-space indentation for nesting. That is input-format knowledge the agent would not get from 'One layer, component or token name per line' alone.

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?

States a specific verb and resource ('audits names') and enumerates exactly what is classified (kebab, snake, camel, Pascal, etc.) and what is flagged. An agent knows precisely what the tool does, but the description never distinguishes it from close siblings like naming_check or lint_token_names.

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

Usage Guidelines3/5

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

'Works on the pasted names only' scopes the input, and 'It flags inconsistency, not which style is right' sets expectation about output. However, there is no explicit when-to-use guidance and no routing away from the overlapping siblings naming_check and lint_token_names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources