Skip to main content
Glama
woodenriver05

comfyui-reddit-support-finder

by woodenriver05
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Server Quality Checklist

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

  • Latest release: v0.1.0

  • Disambiguation5/5

    With a single tool, there is no possibility of confusion between overlapping tools. The tool's purpose is clearly focused on searching r/comfyui support discussions, so an agent can readily understand what it does.

    Naming Consistency5/5

    The tool name follows a consistent verb_noun pattern with 'search_comfyui_support'. Since it is the only tool, there are no naming style conflicts to evaluate.

    Tool Count3/5

    One tool is at the thin lower bound for an MCP server. It may be sufficient for a narrowly focused finder, but it lacks any additional tools that could enhance flexibility or support follow-up requests.

    Completeness4/5

    The search tool directly satisfies the server's stated purpose of finding troubleshooting discussions. Some minor gaps exist, such as the inability to fetch specific post details or comments, but the core search functionality is well covered.

  • Average 3.9/5 across 1 of 1 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 1 commit in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI status not available

  • 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

  • Behavior3/5

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

    The description states 'Read-only, no storage,' which reinforces the readOnlyHint annotation and adds the small extra context that no storage is used. This is useful, but the annotation already covers the core safety trait, so the description only modestly adds beyond the structured data. No rate limits, pagination, or return format details are disclosed.

    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 two concise sentences with no filler. The main action and object are front-loaded, and the read-only/no-storage behavior is stated in a compact second sentence. Every word 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?

    For a simple search tool with four parameters, an output schema absent, and clear defaults/enums on the schema side, the description gives enough context to select and invoke it. It identifies the resource, topic, and safety profile; the only missing piece is a more explicit description of how sort/time values affect results, but those are still inferable from the schema.

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

    Parameters2/5

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

    Schema description coverage is only 25%, and the description does not explain the 'sort', 'time', or 'limit' parameters; only 'query' is partially reflected via the phrase 'user-requested troubleshooting discussions.' The schema itself only documents 'query', leaving the other three parameters under-specified for an agent, and the description fails to compensate.

    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 names a specific verb and resource: 'Search public r/comfyui posts' and defines the scope as 'user-requested troubleshooting discussions.' It is clearly a search tool for a particular community and topic, which is enough to distinguish it even though no sibling tools are listed.

    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 makes the intended use clear: finding troubleshooting discussions in r/comfyui that match user-requested issues. It does not explicitly state when not to use it or list alternatives, but because there are no sibling tools provided, the clear context is sufficient for a correct call.

    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

comfyui-reddit-support-finder MCP server

Copy to your README.md:

Score Badge

comfyui-reddit-support-finder MCP server

Copy to your README.md:

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/woodenriver05/comfyui-reddit-support-finder'

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