Skip to main content
Glama
CaptainCrouton89

MCP Server Boilerplate

by CaptainCrouton89
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

Server Quality Checklist

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

  • Latest release: v1.0.0

  • Disambiguation5/5

    The two tools have completely distinct purposes: 'get-mcp-docs' is for server creation/documentation, while 'hello-world' is for user interaction. There is no overlap or ambiguity between them.

    Naming Consistency2/5

    The naming is inconsistent: 'get-mcp-docs' uses kebab-case with a verb-object structure, while 'hello-world' uses kebab-case but is a noun-phrase without a clear verb. There is no predictable pattern across the set.

    Tool Count2/5

    With only 2 tools, this server feels too thin for a 'boilerplate' purpose, which typically implies foundational or example functionality. The count is insufficient to demonstrate a coherent toolset for server development.

    Completeness2/5

    For a boilerplate server, there are significant gaps: no tools for configuration, testing, deployment, or common MCP operations like listing or updating. The surface is severely incomplete for the implied domain of server setup and examples.

  • Average 2.4/5 across 2 of 2 tools scored. Lowest: 1.7/5.

    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 status not available

  • Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.

    If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.

    MCP servers without a LICENSE cannot be installed.

  • 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

  • Behavior1/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, but it fails completely. 'Make an MCP server' is vague and doesn't reveal whether this is a read or write operation, what permissions might be required, what side effects occur, or what the tool returns. The description provides no behavioral context beyond the ambiguous verb 'Make,' leaving critical operational characteristics undefined.

    Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

    Conciseness2/5

    Is the description appropriately sized, front-loaded, and free of redundancy?

    While the description is brief ('Make an MCP server'), this brevity represents under-specification rather than effective conciseness. The single sentence fails to convey essential information, making it inefficient rather than well-structured. A truly concise description would front-load critical details, but this one omits them entirely, so it doesn't earn its place as helpful content.

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

    Completeness1/5

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

    Given the tool's complexity (implied by 'Make' suggesting a creation/mutation operation), lack of annotations, and absence of an output schema, the description is severely incomplete. It doesn't explain what 'making' entails, what the tool returns, or any behavioral aspects. For a tool that appears to perform a mutation with no structured safety hints, this description leaves the agent without enough information to use the tool correctly or understand its effects.

    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 single parameter 'name' clearly documented as 'The name of the MCP server.' The description adds no additional meaning or context about this parameter beyond what the schema provides. According to the scoring rules, when schema_description_coverage is high (>80%), the baseline score is 3 even with no parameter information in the description, which applies here.

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

    Purpose2/5

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

    The description 'Make an MCP server' is a tautology that essentially restates the tool name 'get-mcp-docs' rather than clearly explaining what the tool does. It doesn't specify what 'making' entails (e.g., generating documentation, creating server instances, or something else) or what resource it operates on. The description fails to distinguish this tool from its sibling 'hello-world' or provide meaningful context about its specific function.

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

    Usage Guidelines1/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. It doesn't mention any context, prerequisites, or exclusions for usage. There's no indication of how this tool relates to its sibling 'hello-world' or when one should be chosen over the other. The lack of usage information leaves the agent with no basis for making informed decisions about 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?

    With no annotations provided, the description carries full burden for behavioral disclosure. 'Say hello' implies a read-only, non-destructive operation, but the description doesn't explicitly confirm this or provide any additional behavioral context like response format, error conditions, or side effects. It's minimally adequate but lacks important details.

    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 perfectly concise at just four words, front-loading the core functionality with zero wasted words. Every element earns its place, making it immediately understandable without unnecessary elaboration. This is an excellent example of efficient communication.

    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 basic purpose but lacks important context. Without annotations or output schema, the description should ideally mention what the tool returns (e.g., a greeting message) and any behavioral constraints. It's minimally viable but has clear gaps.

    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 description coverage is 100%, with the single parameter 'name' clearly documented as 'The name of the user'. The description doesn't add any parameter information beyond what's in the schema, which is acceptable given the high schema coverage. The baseline score of 3 reflects adequate but not enhanced parameter documentation.

    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's action ('Say hello') and target ('to the user'), making the purpose immediately understandable. It doesn't differentiate from the sibling tool 'get-mcp-docs', but that's reasonable since they serve completely different functions. The description avoids tautology by not just repeating the tool name.

    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 or in what context it should be invoked. It simply states what the tool does without any usage context, prerequisites, or comparison to the sibling tool. This leaves the agent with minimal guidance for tool selection.

    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

mcp-reddit MCP server

Copy to your README.md:

Score Badge

mcp-reddit 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/CaptainCrouton89/mcp-reddit'

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