Skip to main content
Glama
sakebomb

Early MCP

by sakebomb
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

billing_report

Calculate total billable hours and cost for activities tracked within a date range, using an hourly rate. Provides accurate billing amounts.

Instructions

Calculate billable hours and cost by activity.

Args:
    start_date: Start date in YYYY-MM-DD format
    end_date: End date in YYYY-MM-DD format
    hourly_rate: Rate per hour in your currency

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateYes
start_dateYes
hourly_rateYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It mentions calculation but omits side effects, authentication needs, rate limits, or whether operations are read-only, leaving significant gaps.

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?

The description is concise and front-loaded with the purpose, followed by parameter details. The 'Args:' section is slightly redundant with the schema but overall efficient.

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

Completeness2/5

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

Despite having an output schema (not shown), the description fails to explain return values or behavior details such as handling of partial hours, weekends, or currency formatting, making it incomplete for a billing tool.

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?

The description adds meaning beyond the schema by specifying date formats (YYYY-MM-DD) and clarifying that hourly_rate is 'in your currency', compensating for the schema's 0% description coverage. However, it lacks constraints like date range validation or timezone handling.

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 tool calculates billable hours and cost by activity, which is a specific verb+resource combination that distinguishes it from sibling tools like time_summary or efficiency_report.

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?

No guidance is provided on when to use this tool versus alternatives such as time_summary or efficiency_report. The description lacks any context about prerequisites or exclusions.

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

Install Server

Other Tools

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/sakebomb/early_mcp'

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