Skip to main content
Glama
Sign In
EARLY App MCP Server

EARLY App MCP Server

by janfincke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Activities

list_activities
Read-only

Retrieve all activities from EARLY time tracking, optionally filtering to active activities only, to review or select activities for time entries.

Instructions

Get all activities

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
activeOnlyNoIf true, only return active activities. Defaults to false (returns all activities).

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

C2.3/5.0
Behavior2/5

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

The readOnlyHint annotation already establishes this is a safe read, so the description's only job is to add context such as whether all records are returned by default, ordering, or volume/pagination behavior — none of which is stated. "All" hints at unfiltered results, but this is not made explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three words are certainly front-loaded and waste nothing, but the brevity reflects under-specification rather than disciplined compression. There is no structure because there is essentially no content.

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?

For a read-only list tool with one optional flag and no output schema, the description should at minimum convey the resource being listed and the shape of the result set. Neither is present, and the crowded sibling set makes the omission more damaging.

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 single parameter activeOnly is fully documented in the schema, including its default and effect, so the schema carries the semantic load. The description adds nothing about it, which meets the baseline for 100% schema coverage but does not exceed it.

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?

"Get all activities" restates the name and title (List Activities) almost word for word, so it adds no specificity. It does not say what an "activity" is in this domain or how the list differs from the sibling get_time_entries, leaving the agent to infer the 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 when-to-use guidance, no exclusion, and no named alternative among the many siblings (get_time_entries, get_active_timer, generate_report, etc.). The agent must guess when listing activities is the right call versus reading time 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