Skip to main content
Glama

local-mcp

by com.local-mcp

Daily Brief

daily_brief
Read-only

Returns a single morning briefing combining today's calendar events, overdue and due-today reminders, unread inbox email count + subjects, and — when a location is provided — today's weather. Perfect for starting each day: one call gives you everything on your plate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationNoOptional city name or 'lat,lon' to include today's weather in the brief (e.g. 'London', 'San Francisco'). Omitted if not provided.
include_emailsNoInclude unread email summary from Mail.app (default true, skipped gracefully if Mail is not running)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesToday's date (YYYY-MM-DD).
noteNoOnboarding enrichment shown when nothing is scheduled.
emailsYesUnread email summary (unread_count + recent_unread), or {skipped} / {error}, or null when not requested.
eventsYesToday's calendar events.
weatherNoToday's weather (current conditions + forecast), only present when a location was provided.
remindersYesReminders due today or overdue.
incompleteNoSections that could NOT be read this time (each step has its own ceiling). An empty/absent list means every section was actually read; a section named here means its data is missing, NOT that it is empty.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds value by disclosing that including weather is conditional on providing a location and that email integration is gracefully skipped if Mail.app is not running. This provides behavioral context beyond the safety profile.

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?

The description is extremely concise with two sentences. The first lists the data sources, and the second gives the usage recommendation. Every word earns its place; there is no fluff or repetition.

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 tool aggregates multiple sources, has an output schema, and is read-only, the description covers most aspects: what data is included, the optional weather condition, and graceful handling of missing Mail. It is slightly incomplete in not describing behavior when no events/reminders exist, but the output schema likely handles that. Overall very good.

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%, so the baseline is 3. The description does not add any additional parameter meaning beyond what the schema already provides; it merely restates the parameter descriptions when it mentions location for weather. It does not elaborate on the include_emails parameter.

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 returns a 'morning briefing' combining four specific data sources: today's calendar events, overdue and due-today reminders, unread email summary, and optional weather. This distinguishes it from individual data retrieval tools (e.g., list_calendar_events, get_weather) by presenting it as an aggregate, single-call solution for a morning overview.

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

Usage Guidelines4/5

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

The description explicitly recommends using this tool 'for starting each day' and notes it is 'perfect' for getting everything on your plate in one call. While it doesn't explicitly say when not to use it or name alternative tools for deeper dives, the usage context is clear and well-defined for its aggregate purpose.

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

All local-mcp 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.5/5.0
Disambiguation3/5

Many tools are clearly distinct per app (e.g., chrome_*, safari_*, m365_*), but there is notable overlap between generic file tools like `file_list` and `finder_list`, both listing files; `search_contacts` and `list_contacts` serve similar purposes; `report_friction` and `report_problem` both send feedback to the team. The large number of tools with similar purposes in different domains creates moderate ambiguity for an agent.

Naming Consistency4/5

The naming convention is very consistent overall: most tools follow a `{app}_action` or `verb_noun` pattern (e.g., `chrome_click`, `create_calendar_event`, `list_reminders`). There are minor deviations like `lmcp_install_upgrade` (two verbs) and `complete_omnifocus_task` vs. `complete_reminder` (inconsistent verb placement). Still, the pattern is predictable and readable across the full set.

Tool Count2/5

With 225 tools, the surface is extremely large and heavy. While it covers many distinct domains (browsers, mail, calendar, files, notes, reminders, video editing, web automation, etc.), the sheer number makes it hard to navigate and likely includes many rarely-used tools. This is far beyond the well-scoped range of 3-15 tools and feels excessive even for a 'local everything' MCP server.

Completeness3/5

For many app integrations, the tool set provides solid CRUD coverage (e.g., Calendar has create, read, update, delete; Apple Notes has create, read, update, list, search; OmniFocus has create, list, search, complete). However, some areas are incomplete: for example, there is no tool to create a new Mail folder or delete notes. The 'web' tools lack a clear update/delete for saved sessions. The suite is broad but has notable gaps within individual domains.

Resources