Skip to main content
Glama
wiz0floyd

best-practices-mcp

by wiz0floyd
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Server Quality Checklist

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

  • Latest release: v0.1.0

  • Disambiguation5/5

    The two tools have clearly distinct purposes: one lists content types for filtering, the other performs searches across the knowledge base. No ambiguity between them.

    Naming Consistency5/5

    Both tools follow the consistent pattern 'servicenow_verb_noun' (list_content_types and search), making them easily distinguishable and predictable.

    Tool Count4/5

    With only 2 tools, the server is minimal but appropriate for its narrow focus on searching ServiceNow best practices. The helper tool is essential for effective use of the search tool.

    Completeness4/5

    The tool surface covers the core workflows: retrieving valid content types and performing searches with smart fallback. Minor gaps exist (e.g., no tool to fetch a single result in detail), but overall it's well-scoped.

  • Average 4.6/5 across 2 of 2 tools scored.

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

    • No community issues in the last 6 months
    • 14 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

  • Behavior5/5

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

    Discloses no authentication required, automatic content-type detection, routing of query cues, fallback when filter returns nothing, and response fields (searchedQuery, detectedContentType, contentTypeFilterDegraded/note). Fully transparent beyond annotations (none provided).

    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?

    Single paragraph with front-loaded purpose sentence. Contains useful details but slightly verbose; could be more concise. Still well-structured.

    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?

    Covers authentication, filter behavior, fallbacks, and partial response structure. Lacks full response details but acceptable for search tool. Paging (offset/limit) not elaborated beyond schema.

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

    Parameters4/5

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

    Schema coverage is 50% (2/4 parameters described). Description adds meaning: how to discover contentType values, automatic detection, and fallback. Compensates for schema gaps and adds unique semantics.

    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?

    Clearly states the tool searches ServiceNow's public best-practices library (mynow.servicenow.com) across multiple content types. Distinguishes from sibling tool by specifying search functionality.

    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?

    Provides guidance on when to set contentType, how to discover valid values, and fallback behavior. Does not explicitly mention alternatives beyond listing content types, but context is clear.

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

  • Behavior5/5

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

    With no annotations provided, the description fully discloses caching mechanics (backed by real search traffic, warm-up sweep, 6-hour expiry, refresh behavior) and the silent failure mode of incorrect guesses. This provides sufficient transparency for an agent to understand side effects and statefulness.

    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 concise: three sentences that front-load the purpose, then explain why the tool is necessary (cannot guess), and finish with caching details. Every sentence adds value without redundancy.

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

    Completeness5/5

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

    Given only one optional boolean parameter and no output schema, the description fully covers the tool's purpose, rationale, caching behavior, and parameter usage. It is complete for an agent to decide when to invoke it and what to expect.

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

    Parameters4/5

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

    Schema description covers the 'refresh' parameter 100% with a clear description. The tool description adds context about the caching lifecycle and explains when to use refresh, enhancing the semantic understanding beyond the schema alone.

    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 action ('List'), the resource ('content-type values for servicenow_search's contentType filter'), and specifies the content (raw internal table identifiers paired with human-readable labels). It effectively distinguishes from the sibling tool 'servicenow_search' by describing what this tool provides for that search tool.

    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 explicitly warns that the identifiers cannot be guessed and that wrong guesses silently return zero results, implying when to use this tool. It also explains caching behavior and when to set the refresh parameter. However, it does not explicitly state 'use this before servicenow_search to get correct identifiers', though this is strongly implied.

    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

mynow-cli MCP server

Copy to your README.md:

Score Badge

mynow-cli 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/wiz0floyd/mynow-cli'

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