Skip to main content
Glama

query_agenda

Retrieve tasks and events scheduled within a specific date and time range. Filter by project, folder, tags, priority, and more to find exactly what you need.

Instructions

Query scheduled items inside a date/time window.

[Category: Query & Search]  [Auth: V1 + V2]
[Related: query_tasks, get_all_tasks, get_project_tasks]
Multi-value filters accept either a list or a single string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_dtYes
to_dtYes
date_fieldNoscheduled
project_idsNo
project_namesNo
folder_idsNo
folder_namesNo
tagsNo
tag_modeNoany
text_queryNo
keyword_modeNoany
regexNo
exclude_regexNo
search_fieldsNo
time_fromNo
time_toNo
timed_onlyNo
all_dayNo
min_priorityNo
prioritiesNo
has_remindersNo
is_recurringNo
has_checklistNo
parent_onlyNo
subtasks_onlyNo
limitNo
sort_byNodueDate
descendingNo
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions multi-value filters accept list or string, but omits details about pagination, return format, error handling, or what happens if no items match.

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 (three lines) and front-loads the purpose. However, it could be better structured with bullet points for clarity, but overall it is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 28 parameters and no output schema, the description is severely incomplete. It fails to explain what constitutes a 'scheduled item', how the date window works, or the behavior of numerous filters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description adds almost no parameter information beyond a generic note about multi-value filters. All 28 parameters rely solely on the schema, which only provides titles and types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Query scheduled items inside a date/time window,' specifying the verb (Query), resource (scheduled items), and scope (date/time window). The category label 'Query & Search' and related tools list help distinguish it from siblings.

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?

The description lists related tools (query_tasks, get_all_tasks, get_project_tasks) but does not provide guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/KpihX/tick-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server