Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

Enable Service

enable_service
Destructive

Turns a service back ON in LMCP after the user turned it off. Use it when a tool reports that its service is turned off (service_off) or marked «I don't use this» (service_dismissed). A service that is off is turned on directly from an AI client on the computer; through the cloud relay, and for a dismissed one, it needs the person's confirmation: without confirm this describes what comes back and changes nothing; with confirm=true it returns the app to My apps. For Calendar, Reminders and Contacts the OS permission is separate — this tool reports whether macOS has granted it, and where the user must be to accept the dialog (it appears on the Mac running LMCP, which over Cloud Relay may not be where the user is).

Input Schema

NameRequiredDescriptionDefault
confirmNoFor a service marked «I don't use this», or any call through the cloud relay: true after the person confirmed turning it on.
serviceYesService id, e.g. 'calendar', 'reminders', 'contacts', 'mail', 'notes', 'messages', 'teams', 'slack'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "For a service marked «I don't use this», or any call through the cloud relay: true after the person confirmed turning it on.",
+  "type": "boolean"
+}
  2. Added
  3. Removed
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say readOnly=false and destructive=true; the description adds the crucial nuance that a call without confirm is effectively a dry run that changes nothing, and that confirm=true restores the app to My apps. It further discloses that for Calendar/Reminders/Contacts OS permission is separate, that the tool only reports whether macOS granted it, and that the consent dialog appears on the Mac running LMCP — possibly not the user's machine over Cloud Relay.

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?

Purpose and trigger are front-loaded in the first two sentences; the remainder is dense but each clause carries operational meaning (confirm semantics, permission dialog location). The final sentence is a long run-on that could be split for readability.

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?

With no output schema, the description usefully covers the no-confirm return ('describes what comes back') and the side effects of confirm, plus the OS-permission caveat. It doesn't describe the shape of a successful enable response, a minor gap for a two-parameter mutation tool.

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 coverage is 100%, so the baseline is 3; the description goes beyond it by explaining the two distinct triggers for confirm (dismissed service, or any cloud-relay call) and tying service identity to the OS-permission caveat for calendar/reminders/contacts. It stops short of enumerating valid service ids, but the schema already provides examples.

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?

States a specific verb and resource ('Turns a service back ON in LMCP') and scopes it to the recovery case ('after the user turned it off'). It names the exact error markers (service_off, service_dismissed) that identify the situation, which no sibling tool describes.

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?

Explicitly says when to call it — when another tool reports service_off or service_dismissed — and explains the branch conditions: direct/AI-client calls proceed, cloud-relay or dismissed services need confirm. It also states when nothing changes (no confirm) versus when the app is restored to My apps.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources