Skip to main content
Glama

Read a Linof doc

fetch_linof_doc
Read-onlyIdempotent

Read one of Linof's public markdown docs in full, by its path ("/pricing.md") or its https://linof.ai URL. Use it after search_linof_docs, or directly for /index.md (the product overview) and /pricing.md.

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": "fetch_linof_doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe doc's path, e.g. "/pricing.md", or its full URL, e.g. "https://linof.ai/index.md".

Output Schema

NameRequiredDescriptionDefault
urlYes
pathYes
titleYes
markdownYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the bar is lower. The description adds useful context beyond that: the docs are public (no auth implied), retrieval is full rather than excerpted, and both a path and a full https URL are accepted.

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 sentences, zero filler: the core action and scope come first, followed by routing guidance. Nothing could be removed without losing information.

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?

An output schema exists so return values need no explanation, and the single required parameter is fully covered. What's missing is only the explicit relationship to get_linof_pricing, which matters given the sibling set.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter already has an example in the schema, so baseline is 3. The description adds meaning by naming which paths matter (/index.md is the product overview, /pricing.md is pricing), which helps an agent pick a value rather than just format one.

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?

States a specific verb (read) and a specific resource (one of Linof's public markdown docs, in full) with the accepted identifier forms. It differentiates from search_linof_docs but never mentions get_linof_pricing, and even suggests going straight to /pricing.md, which leaves the sibling boundary somewhat ambiguous.

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 concrete routing advice: use after search_linof_docs, or directly for /index.md and /pricing.md as entry points. It's clear about when to use it, but gives no 'when not to use' condition and doesn't resolve the overlap with get_linof_pricing.

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