ainote

tasks_read

Read-onlyIdempotent

Read tasks and task categories. action: tasks | categories (consolidated surface — same handlers as the legacy tools)

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	[tasks] Maximum number of tasks to return (default: 25, max: 500)
`action`	Yes	which operation to run
`offset`	No	[tasks] Number of tasks to skip for pagination (default: 0). Use with limit to fetch additional pages.
`search`	No	[tasks] Search keyword in task content and notes (case-insensitive partial match)
`status`	No	[tasks] Filter by task status
`overdue`	No	[tasks] Filter overdue incomplete tasks (due_date < today)
`sort_by`	No	[tasks] Sort field (default: created_at)
`location`	No	[tasks] Filter by location (partial match, e.g., '여의도', '서울')
`due_today`	No	[tasks] Filter tasks due today
`sort_order`	No	[tasks] Sort order (default: desc)
`category_id`	No	[tasks] Filter by category UUID
`due_date_end`	No	[tasks] Filter tasks with due_date <= this date (ISO 8601 format)
`is_important`	No	[tasks] Filter by important tasks only
`due_date_start`	No	[tasks] Filter tasks with due_date >= this date (ISO 8601 format)
`created_date_end`	No	[tasks] Filter tasks created <= this date (ISO 8601 format)
`has_notification`	No	[tasks] Filter by notification enabled status
`completed_date_end`	No	[tasks] Filter tasks completed <= this date (ISO 8601 format)
`created_date_start`	No	[tasks] Filter tasks created >= this date (ISO 8601 format)
`completed_date_start`	No	[tasks] Filter tasks completed >= this date (ISO 8601 format)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedAug 12, 2026
- addedInput schema / $schema
```
Added value: +"https://json-schema.org/draft/2020-12/schema"
```
AddedAug 8, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description does not need to repeat those. It adds minimal extra context like 'consolidated surface — same handlers as the legacy tools,' but does not disclose response shape, pagination behavior, or filtering nuances beyond what the schema already covers.

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-loaded with the core purpose. The parenthetical about consolidated surface and legacy tools adds context but is slightly jargon-heavy; still, it remains efficient with no redundant words.

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?

The description plus the fully covered input schema and safety annotations provide enough context to invoke the tool correctly. A gap is the lack of an output schema or mention of return format, but the read-only nature and rich parameter descriptions keep this adequate for a complex 19-parameter tool.

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%, with every parameter described in the input schema. The description only restates the action enum ('tasks | categories'), which is already documented in the schema, adding no new semantic value for the remaining 18 parameters.

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 the tool reads tasks and task categories, with a specific action parameter distinguishing the two operations. This distinguishes it from mutation siblings like task_write and delete_task.

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 description implies usage for read-only operations via the verb 'Read', but it does not explicitly specify when to use this tool versus alternatives like task_write or delete_task. The 'consolidated surface' note hints at replacing legacy read tools but provides no concrete when/when-not guidance.

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

All ainote tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0

Disambiguation4/5

Most tools clearly target distinct resources (tasks, docs, graph, sync, env_sync, handoffs, judgments, projects, vault). A few pairs could confuse, like sync_push vs vault_sync (which has a push action) and env_sync_write vs env_sync_txn_push, but descriptions mostly clarify boundaries.

Naming Consistency3/5

Names are predominantly snake_case with a noun_verb pattern (e.g., sync_push, task_write), but there are notable inconsistencies: plural/singular mismatches (dev_docs_read vs dev_doc_write, tasks_read vs task_write), verb-first names (list_papers, get_setup_guide, judgment_submit), and a dotted sub-namespace (env_sync.secret_pull) mixed with flat names (env_sync_txn_push).

Tool Count2/5

35 tools is a large surface for a personal note/sync server. While it spans many domains (auth, tasks, docs, sync, env_sync, graph, etc.), the sheer number feels heavy and likely overwhelms agents with too many choices, especially when several tools are consolidated sub-action surfaces.

Completeness3/5

Most domains have reasonable CRUD coverage (tasks, dev docs, graph, sync, env_sync, vault). However, noticeable gaps exist: memory has no write tool (only read), papers only support listing (no create/update/delete), assumptions have write but no dedicated read or delete, and judgment is effectively submit-and-list only.

Resources

Need Help?