Skip to main content
Glama
AliKarami

MikroMCP

by AliKarami
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Manage PPP Profile

manage_ppp_profile
DestructiveIdempotent

Add, update, or remove PPP profiles on MikroTik RouterOS by name, with dry-run previews and protection for built-in profiles.

Instructions

Add, update, or remove a PPP profile. Idempotent by name. update returns no_change when requested values match. Built-in profiles (default, default-encryption) cannot be removed — RouterOS blocks this and the error is surfaced.

Input Schema

NameRequiredDescriptionDefault
nameYesProfile name — idempotency key
actionYesAction to perform
dryRunNoPreview changes without applying.
commentNoOptional comment
routerIdNoRouter ID; omit to use the default router.
dnsServerNoDNS server IP pushed to client
rateLimitNoRate limit string (e.g. '10M/10M')
localAddressNoLocal IP assigned to router end of PPP link
remoteAddressNoIP or pool name assigned to client
sessionTimeoutNoSession timeout duration string (e.g. '1h')
confirmationTokenNoToken from a prior APPROVAL_REQUIRED response. Re-submit the identical call with this token to confirm the destructive action.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.14.1
    • addedInput schema / properties / confirmationToken
      Added value: +{
+  "description": "Token from a prior APPROVAL_REQUIRED response. Re-submit the identical call with this token to confirm the destructive action.",
+  "type": "string"
+}
  2. Changed3 schema fields changedv1.6.0
    • changedInput schema / properties / dryRun / description
      Previous value: -"Preview changes without applying"New value: +"Preview changes without applying."
    • changedInput schema / properties / routerId / description
      Previous value: -"Target router identifier from the router registry"New value: +"Router ID; omit to use the default router."
    • changedInput schema / required
      Previous value: -[
-  "routerId",
-  "action",
-  "name"
-]New value: +[
+  "action",
+  "name"
+]
  3. Addedv1.5.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructive and idempotent behavior, so the bar is lower, but the description still adds value: idempotency is keyed on name, update returns a no_change signal when values already match, and removal of built-in profiles fails with a surfaced RouterOS error. It stops short of describing the APPROVAL_REQUIRED/confirmationToken flow, though the schema documents that.

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 tight sentences, front-loaded with the action set and then the two behavioral caveats. No filler and every sentence adds information an agent needs.

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?

For a multi-action mutation tool with no output schema, it covers actions, idempotency, and the key failure mode. The main omission is the confirmation/approval workflow, which is only discoverable by reading the confirmationToken parameter description.

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?

With 100% schema description coverage, the schema already documents all 11 parameters, so a 3 is the baseline. The description reinforces that name is the idempotency key but adds no syntax or constraint detail beyond what the schema provides.

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 set (add/update/remove) and resource (PPP profile) in the first sentence, clearly distinguishing it from the sibling list_ppp_profiles and the pppoe/ovpn client managers. An agent can tell at a glance this is the CRUD tool for PPP profiles.

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

Usage Guidelines3/5

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

Conveys what each action does and gives a precondition (built-in profiles cannot be removed), but never says when to prefer this tool over alternatives or what the general call context is. Usage is implied by the enumerated actions rather than explicitly guided.

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

Deploy Server

Other Tools