Skip to main content
Glama

List upcoming deadlines

list_upcoming_deadlines
Read-onlyIdempotent

List the upcoming public deadlines (open and announced) in date order, with their type. open_call is true only for open submission and application calls; registration and decision dates are listed with their type and are never open calls. Set open_calls_only to list open calls only. Filter by research field, category key, and date range. Returns at most 20 deadlines per call; use next_offset for the next page.

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

Input Schema

NameRequiredDescriptionDefault
afterNoFirst deadline date (YYYY-MM-DD). Default: today.
fieldNoResearch field key, for example economics, business or political_science. list_calendars gives the current fields.
limitNoRows per page.
beforeNoLast deadline date (YYYY-MM-DD).
offsetNo
categoryNoCategory key, for example 'economics:macroeconomics', 'finance:asset-pricing' or 'political_science:political-theory'. Use list_calendars to see keys.
open_calls_onlyNoList open submission and application calls only.

Output Schema

NameRequiredDescriptionDefault
totalYesNumber of matching deadlines.
deadlinesYes
next_offsetYesOffset of the next page, or null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / open_calls_only
      Added value: +{
      +  "default": false,
      +  "description": "List open submission and application calls only.",
      +  "title": "Open Calls Only",
      +  "type": "boolean"
      +}
    • addedOutput schema / $defs / DeadlineItem / properties / deadline_type
      Added value: +{
      +  "description": "full_paper, extended_abstract, abstract, panel_proposal, call_for_works, application, registration, notification (a decision date), or empty when not yet typed.",
      +  "title": "Deadline Type",
      +  "type": "string"
      +}
    • addedOutput schema / $defs / DeadlineItem / properties / open_call
      Added value: +{
      +  "description": "True when the deadline is open and asks for a submission or an application. Registration, decision and untyped deadlines are never open calls.",
      +  "title": "Open Call",
      +  "type": "boolean"
      +}
    • changedOutput schema / $defs / DeadlineItem / required
      Previous value: -[
      -  "event_id",
      -  "event_title",
      -  "event_url",
      -  "source_url",
      -  "label",
      -  "date",
      -  "time",
      -  "timezone",
      -  "status",
      -  "event_dates"
      -]New value: +[
      +  "event_id",
      +  "event_title",
      +  "event_url",
      +  "source_url",
      +  "label",
      +  "date",
      +  "time",
      +  "timezone",
      +  "status",
      +  "deadline_type",
      +  "open_call",
      +  "event_dates"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Category key, for example 'jel:E' (economics), 'anzsrc_for:3502' (business) or 'apsa_preprints:public-policy'. Use list_calendars to see keys."New value: +"Category key, for example 'economics:macroeconomics', 'finance:asset-pricing' or 'political_science:political-theory'. Use list_calendars to see keys."
  3. Changed1 schema field changed
    • changedInput schema / properties / field / description
      Previous value: -"Research field: economics, business or political_science."New value: +"Research field key, for example economics, business or political_science. list_calendars gives the current fields."
  4. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so safety needs no restating. The description does add useful behavior: the meaning of the open_call flag and a 20-item page cap. However, 'use next_offset for the next page' conflicts with the documented input parameter 'offset', leaving pagination mechanics ambiguous.

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?

Front-loads the core action and scope, then layers filtering and pagination guidance; each sentence carries information. The final sentence squanders some credibility by naming a pagination field that the input schema calls 'offset'.

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?

An output schema exists, so return-value detail is unnecessary, and the description covers filters, page cap and the open-call distinction adequately for a 7-parameter list tool. Minor gaps remain: how this relates to the search and fetch siblings, and the pagination token naming discrepancy.

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?

With 86% schema coverage the baseline is 3; the description adds genuine meaning by clarifying that registration and decision dates are never open calls and that open_calls_only restricts to submission and application calls. The only misstep is the dangling 'next_offset' reference that does not correspond to any input parameter.

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 verb and resource ('List the upcoming public deadlines (open and announced)'), plus ordering ('in date order') and included types. It is distinguishable from list_calendars and fetch, though it never names the sibling tools it differs from.

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

Usage Guidelines4/5

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

Explains the key selection levers: set open_calls_only for open calls, filter by research field, category key and date range. It gives clear usage context but no exclusions or explicit pointer to an alternative (e.g., use search for past or non-public deadlines).

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