Skip to main content
Glama

Fidget Labs

Read a page as markdown

read_page
Read-onlyIdempotent

Read a page on fidgetlabs.io as markdown: a service, an industry, a solution, an article, a glossary term, the pricing page or the engagement list. Pass the site path, for example /pricing or /services/integrated-marketing. ask_fidget_labs returns the paths to read.

Pages written as components have no markdown version. For those the tool says so and lists the paths that do.

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": {
      "path": "<path>"
    },
    "name": "read_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesA path on fidgetlabs.io starting with one slash, such as /pricing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint false), so the bar is lower, but the description still adds real behavior: some pages have no markdown rendering, and in that case the tool reports the failure and lists the paths that do have one. That discloses a partial-failure mode the agent would otherwise only discover at call time. It does not describe output size or truncation behavior.

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?

Purpose and the path example are front-loaded, and the three short paragraphs each carry distinct information: what it reads, how to supply a path, and the component-page exception. The closing clause ("the tool says so and lists the paths that do") is slightly wordy but still earns its place as the failure-mode disclosure.

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 one-parameter read tool with rich annotations and no output schema, this covers what an agent needs: the resource domain, valid path forms, where paths come from, the return format (markdown), and the known non-markdown exception. Nothing material is left for the agent to infer before calling.

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 the single path parameter already documents the leading-slash requirement plus an example (/pricing) and a pattern. The description's extra examples, notably the nested /services/integrated-marketing form, add mild value about path shape but nothing the schema doesn't already establish. Baseline 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?

States a specific verb and resource ("Read a page ... as markdown") and enumerates the resource subtypes it covers: service, industry, solution, article, glossary term, pricing, engagement list. It also positions itself against the sibling ask_fidget_labs by noting that sibling returns the paths to read, so an agent can tell the two apart without opening either schema.

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?

Gives clear usage context: pass a site path such as /pricing, and get paths from ask_fidget_labs first. It also states the exclusion case — pages written as components have no markdown version — which is a genuine when-this-fails condition. It stops short of an explicit when-to-use-this-vs-other-tools comparison beyond the ask_fidget_labs pointer.

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.