Skip to main content
Glama

Read a file on a Flowershow site

read-file
Read-only

Get the current text of one file on one of the signed-in user's Flowershow sites, e.g. index.md. Use it before changing a page that is already on the site, then publish the whole updated file, so the parts you didn't mean to change stay as they are. Text files only (Markdown, HTML, CSS, JS, JSON, ...), up to 256 KB. Get siteId from list-sites and paths from list-files. If the user is not signed in yet, calling it asks them to sign in to Flowershow first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "siteId": "<siteId>",
      "path": "<path>"
    },
    "name": "read-file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath of the file, as returned by list-files
siteIdYessiteId of the site, from list-sites

Output Schema

NameRequiredDescriptionDefault
pathYes
siteIdYes
contentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and non-destructive, but the description adds substantial context beyond them: a 256 KB size ceiling, a text-files-only restriction, and the fact that a call triggers a sign-in prompt when the user is unauthenticated. Return-format detail is omitted, but an output schema exists, so that gap is acceptable.

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: purpose first, then workflow guidance, then limits and prerequisites. Every sentence carries information an agent needs, with no filler or repetition of the title.

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 two-parameter read tool with full schema coverage, full annotations, and an output schema, the description covers size limits, file-type scope, id provenance, and the auth-prompt behavior. Only edge cases such as file-not-found or error handling are left unstated, which is a minor gap.

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 description coverage is 100% and both parameter descriptions already explain that path comes from list-files and siteId from list-sites, so the description mostly restates provenance. Baseline 3 applies; no additional format or validation detail is added.

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 ('Get the current text of one file'), names the scope ('one of the signed-in user's Flowershow sites'), and gives a concrete example ('index.md'). It is clearly distinguishable from siblings like list-files and publish.

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 use it ('before changing a page that is already on the site') and why (preserve unintended parts when republishing). It also routes the agent to list-sites for siteId and list-files for paths, so the prerequisites are unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.