design-critique-mcp

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation4/5
critique_design encompasses the focused analyze_* tools, which could cause selection ambiguity, but the descriptions clearly distinguish comprehensive critique from targeted analysis. check_color_contrast is a specific utility that overlaps slightly with analyze_accessibility but serves a distinct quick-check purpose.
Naming Consistency5/5
All tools follow a clear verb_noun pattern: analyze_* for focused analyses, critique_design for the comprehensive critique, and check_color_contrast for a specific check. The pattern is consistent and predictable.
Tool Count5/5
With 6 tools, the server is well-scoped for its purpose. Each tool covers a distinct aspect of design critique, and the count feels appropriate—not too sparse, not overwhelming.
Completeness5/5
The tool set covers the full spectrum of design critique: overall design, color, layout, typography, and accessibility. No obvious gaps exist for the stated purpose, and the combination of a comprehensive critique plus focused analyses provides flexibility.
Average 3.2/5 across 6 of 6 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI is failing
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description should disclose behavioral traits, but it only gives a high-level purpose. It does not mention that the tool is read-only, what input it requires (beyond schema), or what output it returns. This is a significant gap for an analysis tool.
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 six-word phrase with no unnecessary words. It is efficient and front-loaded, though extremely brief.
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?
Despite complete schema coverage, the description is incomplete for tool selection and invocation. There is no output schema, no behavioral details, and no explanation of what 'analysis' returns. The agent is left without sufficient context to know what to expect.
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 already covers both parameters with descriptions (100% coverage). The description adds no parameter-specific meaning, so the baseline of 3 is appropriate.
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 'Analyze visual composition and layout structure' clearly states the tool's purpose with a specific verb ('Analyze') and resource ('visual composition and layout structure'). It distinguishes from color, typography, and accessibility siblings, though it may overlap with critique_design.
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 usage guidance is provided. The description does not mention when to use this tool over alternatives, nor does it specify any exclusions or prerequisites. Sibling tools exist, but there is no reference to them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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. It reveals only that the tool checks a contrast ratio, but it doesn't state what the output is (e.g., numeric ratio, pass/fail), whether WCAG levels are considered, or any edge cases like invalid color formats. This is minimal behavioral disclosure.
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, front-loaded sentence that is appropriately concise for a simple function. Every word adds value, and it avoids unnecessary elaboration or visual clutter.
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?
The tool is simple with no output schema, so the description should clarify what the tool returns. It only says 'check contrast ratio', leaving the result format ambiguous. With no alternatives or caveats mentioned, the description is incomplete for an agent expecting to act on results.
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 schema has 100% description coverage for both parameters (foreground and background), so the baseline is 3. The description doesn't add any meaning beyond what the schema already provides; it merely says 'two specific colors', which is implied by the parameters.
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's function: 'Check contrast ratio between two specific colors'. This is a specific verb (check) and resource (contrast ratio), and it distinguishes from siblings like analyze_color_scheme and analyze_accessibility by focusing on the contrast ratio between two explicit colors.
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 such as analyze_accessibility or analyze_color_scheme. It doesn't mention any context, prerequisites, or exclusions, leaving the agent without direction for tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavior. It lists analysis areas but does not explain how the critique is delivered, what the output format is, or any limitations (e.g., image requirements, processing behavior). For a tool with no output schema, this is a significant gap.
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, concise sentence that front-loads the primary purpose ('comprehensive design critique') and lists key analysis dimensions. Every word contributes value, with no redundancy or filler.
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 the tool has 4 parameters including a nested object, and no output schema, the description should clarify what the critique includes structurally (e.g., sections, scores, text output). It only lists topics covered, leaving return format and usage context unexplained. This is inadequate for a tool of this complexity.
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?
Schema description coverage is 100%, so parameters are already documented in the schema. The description adds little beyond naming analysis topics (composition, color, etc.), which loosely relate to parameters like design_type and brand_guidelines. It does not meaningfully enhance parameter understanding beyond the schema.
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 provides a comprehensive design critique covering composition, color harmony, typography, and accessibility. This distinguishes it from sibling tools that focus on individual aspects, though the verb 'provide' is generic. It communicates the resource and scope well.
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?
The description implies use when a holistic design evaluation is needed, as opposed to the more focused sibling tools. However, it does not explicitly state when to use this tool versus the others, nor does it mention exclusions or prerequisites. Usage context is only tacit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden for behavioral disclosure. It states what is analyzed (contrast, color blindness, WCAG compliance) but does not mention what the tool returns (e.g., pass/fail, score, list of issues), how it processes input, or any limitations. For an analysis tool, this leaves significant ambiguity about expected output and side effects.
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 focused sentence that front-loads the core purpose and lists key aspects. It is concise without being under-specified; every word adds value. It could arguably be slightly longer to include behavioral details, but that is a completeness concern, not a conciseness issue.
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 the tool has no output schema and no annotations, the description should explain what the analysis produces. It does not. It also omits any context about when to use this tool versus check_color_contrast or analyze_color_scheme. The one-paragraph description is complete only for stating the broad topic, not for practical invocation.
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% coverage for the only parameter 'image_data', already described as 'Base64 encoded image data'. The tool description adds no additional meaning about parameters. Baseline 3 applies because the schema fully documents the parameter, so no deduction is warranted, but there is no added value from the description.
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 uses a specific verb 'Analyze' with a clear resource 'design accessibility' and enumerates distinct aspects (contrast, color blindness, WCAG compliance). This distinguishes it from sibling tools like check_color_contrast, which focuses narrowly on contrast, and critique_design, which is broader design feedback. The purpose is unmistakable.
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?
The description implies the tool is used for accessibility analysis but provides no explicit guidance on when to choose this over alternatives. There are no exclusions or references to sibling tools. It gives enough context to infer usage for accessibility-related queries, but not more.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the full burden of behavioral disclosure, but it does not. It only states the action without describing any side effects, output format, limitations, or required permissions. 'Analyze' implies read-only, but the description does not explicitly confirm this or disclose any other behavioral traits, earning a low transparency score.
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, front-loaded sentence that states the verb and target clearly with zero wasted words. It is concise and directly conveys the core purpose.
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?
The tool is simple with one parameter fully described, but the lack of an output schema and lack of any mention of the return format leaves a gap. The description tells what it analyzes but not what the agent can expect as a result, making it minimally complete but not fully self-sufficient.
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 schema has 100% coverage for the single parameter 'image_data' with its description 'Base64 encoded image data'. The tool description adds no new parameter-level meaning beyond what the schema already provides. Baseline is 3, which is appropriate.
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 uses the specific verb 'Analyze' with a clear resource ('color palette and harmony') and context ('in a design'). It is distinguishes itself from sibling tools like analyze_layout, analyze_typography, and analyze_accessibility, and from check_color_contrast which focuses on contrast rather than overall palette harmony.
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 explicit when-to-use or when-not-to-use guidance is provided. The description does not mention alternatives or any exclusions, leaving the agent to infer usage solely from the name and purpose. This is similar to the 'update_drive' example which scored 2 for lacking usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavior. It does not mention that the tool requires base64-encoded image data, nor what it returns (e.g., a report or scores). It only names the analysis dimensions, offering no insight into side effects, limitations, or output format.
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, front-loaded sentence with no unnecessary words. It immediately states the verb and the focus areas, making it highly concise and easy to parse.
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?
For a simple tool with one parameter and no output schema, the description provides the core purpose but leaves out input requirements and return type. Since there are no annotations to fill this gap, the description is minimally sufficient but not fully complete for an AI agent to know what to expect.
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 provides 100% coverage for the single parameter (image_data), describing it as base64-encoded image data. The description does not add further parameter-specific meaning, but since the schema fully documents the parameter, the baseline of 3 applies.
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's function: analyzing typography hierarchy, readability, and font usage. It uses a specific verb ('analyze') and resource ('typography'), and the focus on typography naturally distinguishes it from sibling tools like analyze_color_scheme and analyze_layout.
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?
While the description implies usage for typography-related analysis, it does not explicitly state when to use this tool over alternatives, nor does it provide any exclusion criteria or contextual prerequisites. The user must infer from the name and description that it is for evaluating font and text presentation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![design-critique-mcp MCP server](https://glama.ai/mcp/servers/haasonsaas/design-critique-mcp/badges/card.svg)](https://glama.ai/mcp/servers/haasonsaas/design-critique-mcp)

Score Badge

Copy to your README.md:

[![design-critique-mcp MCP server](https://glama.ai/mcp/servers/haasonsaas/design-critique-mcp/badges/score.svg)](https://glama.ai/mcp/servers/haasonsaas/design-critique-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/haasonsaas/design-critique-mcp'

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