Skip to main content
Glama
Sign In
EARLY App MCP Server

EARLY App MCP Server

by janfincke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Generate Report

generate_report
Read-only

Generate a summary report of time entries for a specified date range, optionally filtered by project, to review tracked work for a period.

Instructions

Generate a summary report of time entries for a given period

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "generate_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateYesEnd date in YYYY-MM-DD format
projectIdNoFilter by activity ID (optional)
startDateYesStart date in YYYY-MM-DD format

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.5
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv2.0.1

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint annotation already tells the agent this is a safe, non-mutating call, and the description is consistent with that. The description adds the period-scoping behavior but says nothing about how the report is aggregated or formatted, which matters given there is no output schema.

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?

A single front-loaded sentence with no filler. It is efficient but so short that no distinguishing or return-value detail is included.

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?

With no output schema and a 'summary report' that could mean many things, the description should say what the report contains or how it differs from a raw listing. It covers the inputs implicitly through the schema but leaves the output and sibling distinction ambiguous.

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%, so startDate, endDate, and projectId are already documented, and the description only restates the date-range concept without adding format or semantics. Baseline 3 is appropriate since the schema carries the full parameter burden.

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 states a specific verb and resource ('Generate a summary report of time entries') plus scope ('for a given period'), so the agent knows exactly what the tool produces. It does not distinguish itself from siblings like get_time_entries, which overlaps heavily on the same resource.

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?

There is no guidance on when to use this instead of get_time_entries, which reads the same underlying data, nor any mention of prerequisites or typical use cases. The agent is left to infer that 'report' means aggregated rather than raw entries.

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

Deploy Server

Other Tools