Skip to main content
Glama
bottlesun

today-work-log

by bottlesun
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

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 confusion or overlap. The tool's purpose is clearly defined and distinct.

    Naming Consistency5/5

    The single tool name follows a clear verb_noun pattern ('get_todays_git_diff'), which is consistent and descriptive. No other names exist to introduce inconsistency.

    Tool Count2/5

    A single tool feels too thin for a server named 'today-work-log', which implies a broader scope such as logging or summarizing work. The narrow utility might justify one tool, but the name suggests more expected functionality.

    Completeness2/5

    The server only extracts today's git diff, but lacks any tools for actually creating or managing work logs, or for retrieving historical data. This significant gap means agents cannot complete a full work-log workflow.

  • Average 3.7/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
    • 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

  • Behavior2/5

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

    With no annotations, the description carries the full burden of behavioral disclosure. It clarifies the time window (midnight to now) and that both commits and diffs are extracted, but it does not explain important aspects such as whether the relevant date is the commit date or author date, whether uncommitted changes are included, what branches are considered, or what the output format looks like. This leaves significant ambiguity for a git-related tool.

    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 sentences, both informative and free of redundancy. It fronts the core action and scope, then adds the use-case context, all without waste.

    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 one-parameter tool, the description is functionally adequate, but it omits details about the output format and error behavior. Since there is no output schema and no annotations, the agent must infer what the tool returns and how edge cases are handled. This is a clear gap, but given the tool's simplicity, the description is not critically incomplete.

    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 already covers the sole parameter fully (repo_path, with an example). The description does not add any new meaning beyond the schema; it merely restates that it applies to a 'local Git repository'. Since schema coverage is 100%, the baseline of 3 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 states a specific verb ('extracts'), a clear resource ('local Git repository'), and a specific scope ('commits and code changes (diff) after midnight today'). It also mentions the intended use case, making the tool's function immediately clear. Since there are no sibling tools, differentiation isn't required.

    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 mentions usage contexts ('useful for TIL (Today I Learned) writing or summarizing work history'), giving the agent clear guidance on when to invoke it. However, it does not provide any exclusions or contrast with alternatives, likely because no siblings exist, but the use-case context is sufficient for a standalone tool.

    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

today-work-log-mcp MCP server

Copy to your README.md:

Score Badge

today-work-log-mcp 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/bottlesun/today-work-log-mcp'

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