Skip to main content
Glama

Workotron Skills

Read a page

read
Read-onlyIdempotent

A page of the directory as markdown: a listing's page with who it is for, what it does, when to use it, its files and its discussion; a business area's, a platform's or a tag's whole list; the Users Forum and Announcements channels and their threads. With no address it answers the first page, which says what the directory holds and links every business area. A page longer than 60,000 characters comes in parts: a part that is not the last ends with a line that says which from reads the next part. A skill's file, at the address take lists for it, comes as its text, for an app that cannot fetch that address itself: the first line, in square brackets, states the file's size and SHA-256 and is not part of the file, and everything after it is the file as it is. Write it unchanged and check its SHA-256. A file that is not text, or is larger than 256 KB, is fetched at its address.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoThe character to read from, as the last line of an earlier part says. 0 when absent.
addressNoThe page's address: a full address from a search result or a page's link, or its path, like `unpaid-invoice-chaser` or `skills/finance`. Absent for the first page. Or the address of a skill's file, as take lists it, like `unpaid-invoice-chaser/files/SKILL.md`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, and the description adds real behavior on top: pages over 60,000 characters are split with a continuation line naming the next `from` value, skill files carry a bracketed size/SHA-256 header that is not part of the file, and non-text or >256KB files are fetched at their address instead. The phrasing of the continuation rule ('a line that says which from reads the next part') is awkward but the substantive disclosure is strong.

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?

It is front-loaded — the resource type and format come first, followed by pagination and file handling — and each clause covers a distinct case rather than repeating itself. It is nonetheless one long, hard-to-parse passage with awkward constructions that slow an agent's reading.

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 no output schema, the definition covers the important edge cases: default first page, large-page splitting, skill-file framing with a SHA-256 check instruction, and the fallback for binary or oversized files. What is missing is minor — no note on error behavior for an invalid address.

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%, so both `from` and `address` are already documented in the input schema, setting the baseline at 3. The description mostly restates those semantics (path forms, absent-for-first-page, use of `from` from an earlier part) rather than adding syntax or constraints the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening clause names a specific verb and resource — 'A page of the directory as markdown' — and enumerates which page types qualify (listing pages, business-area/platform/tag lists, forum channels). It is clear what is returned, but the enumeration is delivered as a dense run-on list and the tool never explicitly contrasts itself with siblings like search or take.

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?

It gives one concrete usage rule — 'With no address it answers the first page, which says what the directory holds' — and a routing rule for skill files ('at the address take lists for it'). However, there is no explicit when-not-to-use guidance and no statement of when an agent should prefer search or take instead of read.

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.

Resources