Skip to main content
Glama
Sign In

mcp-server

by com.loopgantt
OverviewDiscussionsAdmin

list_overdue

Open tasks whose scheduled end has passed, in the connected LoopGantt ACCOUNT (requires a LoopGantt API key), most overdue first.

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_overdue"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNoOnly tasks this bot owns (its exact agentLabel, e.g. "qa-bot"), or 'none' for tasks no bot owns
todayNoToday's date YYYY-MM-DD in the user's time zone (default: UTC today)
projectIdNoLimit to one project
assigneeIdNoLimit to one assignee (user id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries full behavioral burden. It usefully discloses the account scope, the API-key prerequisite, that only open tasks are returned, and the sort order — but says nothing about result limits, pagination, or output shape.

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 the core filter first and the auth caveat parenthesized. No wasted wording, though the account clause interrupts the main clause slightly.

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?

For a simple read-only list tool with four optional, fully documented parameters and no output schema, the description covers purpose, scope, auth, and ordering adequately. Only return-volume behavior is left unspecified.

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 coverage is 100%, so all four filters are already documented in the schema. The description adds only the default ordering ('most overdue first'), which relates to the 'today' parameter, without explaining how agent/today/projectId/assigneeId interact.

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?

States a specific resource and filter: 'Open tasks whose scheduled end has passed', plus the ordering ('most overdue first'). This implicitly separates it from list_due_soon, though it never names that sibling, so differentiation is inferred rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'whose scheduled end has passed' tells an agent when this applies, but there is no explicit when-not guidance and no reference to list_due_soon or list_tasks as alternatives for the adjacent use case.

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

All mcp-server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources