Skip to main content
Glama

Outlook Mail

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.6/5.0
Behavior4/5

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

Annotations give idempotentHint=true and destructiveHint=false. The description adds value by explaining persistence details (24-hour retention for anonymous, persistent for authenticated) and the scoping mechanism. However, it doesn't discuss idempotency implications or confirm read/write behavior beyond what's in annotations.

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, front-loaded with purpose, then usage, then behavioral details. Each sentence adds value; no redundancy.

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?

Given the simplicity of the tool (2 params, no output schema), the description is mostly complete. It explains scope, persistence, and pairing. Minor gap: doesn't mention if key can be overwritten or if storage is case-sensitive.

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 covers both parameters with descriptions. The description adds practical usage examples and naming conventions (e.g., 'subject_property') that go beyond the schema. However, it doesn't provide format or length constraints.

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 action ('Save data'), the resource ('key-value pair'), and the context ('across conversations/sessions'). It distinguishes from sibling tools like 'recall' and 'forget' by explicitly mentioning pairing.

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?

Provides explicit guidance on when to use the tool: 'when you discover something worth carrying forward' with concrete examples. Also tells when not to use implicitly by pairing it with recall/forget, and specifies scope (by identifier).

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

All Outlook Mail 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.6/5.0
Disambiguation2/5

The set contains multiple near-duplicate tools: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded overlap heavily (beta is explicitly identical right now), and discover_tools vs suggest_questions both serve a 'what can I do' purpose. The server name 'Outlook Mail' also misleads since only 5 of 36 tools are email-related, creating domain confusion.

Naming Consistency4/5

Most tools follow a readable snake_case verb_noun or prefixed pattern (outlook_list_messages, polymarket_edges, ask_pipeworx). Minor deviations like ai_visibility_check (instead of check_ai_visibility) and pipeworx_feedback/pipeworx_trending (noun-first) are present but don't seriously obscure meaning.

Tool Count2/5

36 tools is well beyond a typical well-scoped set, and the vast majority belong to unrelated Pipeworx/Polymarket domains while the server claims to be Outlook Mail. The count is padded by redundant variants (ask_pipeworx_beta, multiple polymarket scanning tools) that could be consolidated.

Completeness2/5

For the stated Outlook Mail purpose, the surface is read-only: you can list, search, and get messages/profile/folders, but there is no send, reply, delete, move, or mark-as-read capability—an obvious dead end for email workflows. The broader data-research side is more extensive but still lacks update paths for subscriptions/memories.

Resources