Skip to main content
Glama

Todoist

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

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

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations provide idempotentHint=true, destructiveHint=false. Description adds that memory is key-value scoped by identifier and explains persistence, going beyond annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise and well-structured: purpose first, then usage, then details. Every sentence adds value without redundancy.

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

Completeness5/5

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

Given simple parameters and no output schema, description fully covers what the agent needs: what to store, when, pairing with recall/forget, scope, and persistence.

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?

Schema has 100% coverage with descriptions. Description adds contextual examples (e.g., 'subject_property') and clarifies scope, enhancing but not requiring additional info beyond schema.

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's purpose: 'Save data the agent will need to reuse later' with concrete examples (resolved ticker, target address, user preference). It distinguishes itself from siblings like recall and forget.

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

Usage Guidelines5/5

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

Explicit guidance: 'Use when you discover something worth carrying forward' and pairs with recall/forget. Also details persistence differences for authenticated vs anonymous sessions, helping the agent decide when to use this tool.

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

All Todoist toolsInspect
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.8/5.0
Disambiguation3/5

Tools have overlapping purposes, e.g., 'ask_pipeworx' and 'validate_claim' both handle factual queries; 'bet_research' and 'polymarket_edges' both analyze betting markets. However, most tools target distinct domains (Todoist, data lookup, betting), so some separation exists.

Naming Consistency3/5

Naming uses snake_case and often follows verb_noun, but prefixes are inconsistent: some tools have 'todoist_', 'pipeworx_', 'polymarket_', while others like 'compare_entities' and 'discover_tools' lack prefixes. This mix reduces predictability.

Tool Count2/5

25 tools is high, and only 5 are Todoist-specific despite the server name. The inclusion of many unrelated tools (Pipeworx, betting, etc.) makes the set feel bloated and misaligned with the server's stated focus.

Completeness2/5

For Todoist, the set lacks create/update/delete operations, leaving gaps. For the broader data domains, coverage is extensive but unfocused. The server's purpose is unclear, leading to an incomplete surface for any single use case.

Resources