Skip to main content
Glama

Microsoft Todo

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?

Discloses key-value storage, scoping by identifier, and persistence duration (24h/anonymous vs persistent/authenticated). Annotations support non-destructive, non-readOnly, idempotent behavior.

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?

Three concise sentences, front-loaded with purpose. No fluff; every sentence adds essential context.

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?

Covers all needed context: purpose, when to use, behavior, persistence, and relation to siblings. No gaps given tool simplicity.

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 already describes both parameters with examples. Description adds value by providing usage conventions for keys and value 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?

Clear verb+resource ('Save data') with explicit purpose ('reuse later'). Distinguishes from sibling tools '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?

States when to use ('when you discover something worth carrying forward') and mentions pairing with recall/forget. Also scoping and persistence details.

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

All Microsoft Todo 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

B3.4/5.0
Disambiguation1/5

The set is dominated by overlapping Pipeworx and prediction-market tools, with ask_pipeworx and ask_pipeworx_beta explicitly described as currently identical, and ask_pipeworx_grounded, deep_research, and discover_tools serving heavily overlapping lookup purposes. The four Microsoft To Do tools are buried among 31 unrelated tools, making it very hard for an agent to select the right tool for the server's apparent domain.

Naming Consistency2/5

Most names are snake_case, but the naming conventions are otherwise mixed: there are verb_noun tools like list_tasks and get_task, bare verbs like remember/forget/recall, prefixed families like polymarket_*, and noun-phrase names like entity_profile, recent_changes, and pipeworx_trending. The lack of a consistent pattern across the set, especially relative to the Microsoft To Do server name, makes naming unpredictable.

Tool Count1/5

35 tools is already heavy, but the bigger problem is that only 4 of them are for Microsoft To Do, the server's stated name and purpose. The remaining 31 tools belong to unrelated Pipeworx data, prediction-market, and memory-management domains, which is an extreme scope mismatch.

Completeness1/5

For a Microsoft To Do server, the surface is severely incomplete: list_task_lists, list_tasks, get_task, and find_due_tasks cover reading and browsing only, with no create, update, complete, or delete operations. Even the broader Pipeworx functionality is scattered and redundant rather than forming a coherent domain surface.

Resources