Skip to main content
Glama
Sign In
Nekoweb MCP Server

Nekoweb MCP Server

by Menal226
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Read file

nekoweb_read_file
Read-onlyIdempotent

Reads the raw source of a Nekoweb site file, returning HTML with SSI directives unrendered and text paginated by character offset; images up to 5 MB return as images, other binaries as size.

Instructions

Read the raw source of a file on your Nekoweb site (SSI directives in .html files are returned as written, not rendered).

Text files are returned as text, paginated by character offset. Images up to 5.0 MB are returned as images. Other binaries return only their size.

Examples:

  • "Show me my homepage HTML" -> { path: "/mysite.nekoweb.org/index.html" }

  • "Read the rest of the stylesheet" -> { path: "/mysite.nekoweb.org/style.css", offset: 20000 }

Input Schema

NameRequiredDescriptionDefault
pathYesPath from the account's file root, including the site folder, e.g. '/mysite.nekoweb.org/index.html'
offsetNoCharacter offset to start reading from, for files longer than max_chars
max_charsNoMaximum characters of text to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish a safe, idempotent read, and the description adds substantial behavior beyond them: SSI directives are not rendered, text is paginated, images up to 5.0 MB are returned as images, and other binaries return only size.

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?

It front-loads the core raw-source behavior, then compactly explains file-type-dependent returns and provides two useful examples. Every sentence contributes to selecting or correctly invoking the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read tool with full annotations and no output schema, it explains return behavior by file type, pagination via offset, SSI handling, and binary size reporting. An agent has enough information to call it correctly in typical cases.

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 path, offset, and max_chars are already well documented in the input schema. The description reinforces offset usage through the 'Read the rest' example, but adds little 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, 'Read', and resource, 'raw source of a file on your Nekoweb site', while clarifying the important SSI behavior. It is clearly distinguishable from sibling write/delete tools without needing schema inspection.

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 examples give concrete when-to-use context, including continuing a paginated read with offset. However, it does not explicitly name alternatives or when-not conditions, such as using list_folder to discover paths.

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