Skip to main content
Glama
AliKarami

MikroMCP

by AliKarami
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Get File Content

get_file_content
Read-onlyIdempotent

Retrieve text file contents from MikroTik routers for inspection or troubleshooting. Provide the exact file name to read its content directly.

Instructions

Read a text file's contents from a MikroTik router. Only suitable for text files — binary files will return garbled content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesExact file name on the router (e.g. flash/script.rsc)
routerIdNoRouter ID; omit to use the default router.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv1.6.0
    • 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",
-  "name"
-]New value: +[
+  "name"
+]
  2. Addedv1.5.0
  3. Removedv1.1.0
  4. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate read-only and idempotent behavior. The description adds a critical behavioral note about binary files causing garbled output, which is not captured in structured fields.

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?

Two concise sentences with no extraneous information. Every word adds value.

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?

No output schema, so the description could specify return format (e.g., plain text). However, given the simple read operation and rich annotations, the current description is nearly complete.

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% and parameter descriptions are adequate. The description does not add new meaning beyond the schema, so a baseline score of 3 is appropriate.

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 'Read a text file's contents from a MikroTik router,' providing a specific verb and resource. It effectively distinguishes from sibling tools like upload_file or delete_file.

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?

Explicitly warns that binary files return garbled content, guiding the agent to use this tool only for text files. Does not name alternative tools for binary files, but the guidance is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AliKarami/MikroMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server