Skip to main content
Glama
StevenStavrakis

MCP Server Starter

by StevenStavrakis
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

Server Quality Checklist

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

  • Latest release: v1.0.0

  • Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'hello_tool' stands alone with a distinct purpose, making it impossible for an agent to misselect among alternatives.

    Naming Consistency5/5

    A single tool inherently follows a consistent naming pattern, as there are no other tools to compare it against. The name 'hello_tool' uses snake_case and a clear verb-noun structure, which would be consistent if more tools were added.

    Tool Count2/5

    A single tool is too few for most server purposes, as it limits functionality and suggests an incomplete or trivial implementation. For a server named 'MCP Server Starter', which implies a foundational or example setup, one tool feels insufficient to demonstrate meaningful capabilities.

    Completeness1/5

    With only a 'hello_tool', the server lacks any substantial coverage of a domain. There are obvious gaps, as no CRUD operations, lifecycle management, or core workflows are provided, making it severely incomplete for any practical use case.

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

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

    • No issues in the last 6 months
    • No commit activity data available
    • 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

  • Behavior1/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 of behavioral disclosure. 'Hello tool' gives no information about whether this is a read/write operation, what permissions might be required, what side effects occur, or what the tool actually does. It fails completely to describe behavioral traits.

    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 technically concise with just two words, this represents under-specification rather than effective conciseness. The description is too brief to be useful, failing to communicate essential information. Every sentence should earn its place, but here the single 'sentence' doesn't earn its place by providing meaningful 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 that this is a tool with no annotations, no output schema, and a minimal description, the description is completely inadequate. For even a simple tool, 'Hello tool' provides insufficient context about what the tool does, when to use it, or what behavior to expect. The description fails to meet minimum requirements for completeness.

    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%, with the schema clearly documenting the single 'name' parameter. The description adds no parameter information beyond what's in the schema, but with complete schema coverage, the baseline score is 3. The description doesn't compensate for any gaps because there are none in the schema.

    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 'Hello tool' is a tautology that merely restates the tool name without specifying what it does. It doesn't provide a clear verb+resource combination or explain the tool's function beyond its name. While it doesn't actively mislead, it fails to communicate the tool's purpose effectively.

    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 absolutely no guidance about when to use this tool, what context it's appropriate for, or any alternatives. With no sibling tools mentioned, the bar is lower, but the description still offers zero usage information, leaving the agent with no context 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-starter-template MCP server

Copy to your README.md:

Score Badge

mcp-starter-template 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/StevenStavrakis/mcp-starter-template'

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