Skip to main content
Glama

list_due

List forecasts whose due date falls in the inclusive window from…to (YYYY-MM-DD). Returns public and MCP-only entries, including already closed ones in that window. Signetex grades evidence and issues no true/false verdicts.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "list_due"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesEnd of the due-date window, inclusive, YYYY-MM-DD.
fromYesStart of the due-date window, inclusive, YYYY-MM-DD.

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?

With no annotations, the description carries the behavioral burden and does disclose useful traits: inclusion of public and MCP-only entries, inclusion of closed entries, and that no true/false verdicts are issued. It does not cover ordering, pagination, or response 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?

The description is short and front-loads the core behavior. The final sentence about evidence grades is relevant context, though slightly tangential to the listing operation itself.

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 two-parameter list tool with no output schema and no annotations, the description gives enough context to call it correctly. It could be stronger with ordering or return-structure details, but nothing essential is missing.

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%, and the schema already documents from/to as inclusive YYYY-MM-DD bounds. The description reinforces the inclusive window but adds no parameter meaning beyond the schema.

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: listing forecasts by due-date window. It is clear about scope, including inclusive dates and closed entries, though it does not explicitly differentiate itself from similarly named siblings such as due_forecasts.

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?

Usage is implied by the due-date window framing, but there is no explicit guidance on when to choose this over alternatives. It also does not state any exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources