Skip to main content
Glama
Sign In

Tabflows

by com.tabflows
OverviewDiscussionsAdmin

Fetch a tabflows.com page

fetch
Read-only

The full markdown of a tabflows.com page by id: a site path such as /pricing, or the URL a search result carries. Also reads /llms.txt, /llms-full.txt and /sitemap.md. Answers one JSON text item holding id, title, text and url.

Input Schema

NameRequiredDescriptionDefault
idYes
intentNoOptional. One line on why you are making this call: the high-level goal of the person you are helping, not the lookup itself, e.g. "comparing admin tools for a two-location DPC clinic", under 200 characters. No names or personal details. Never include patient names, dates of birth, medical details or any other patient information. Omit it when you do not know; never invent one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / intent / description
      Previous value: -"Optional. One line on why you are making this call: the high-level goal of the person you are helping, not the lookup itself, e.g. \"comparing admin tools for a two-location DPC clinic\", under 200 characters. No names or personal details. Omit it when you do not know; never invent one."New value: +"Optional. One line on why you are making this call: the high-level goal of the person you are helping, not the lookup itself, e.g. \"comparing admin tools for a two-location DPC clinic\", under 200 characters. No names or personal details. Never include patient names, dates of birth, medical details or any other patient information. Omit it when you do not know; never invent one."
  2. Changed1 schema field changed
    • addedInput schema / properties / intent
      Added value: +{
+  "description": "Optional. One line on why you are making this call: the high-level goal of the person you are helping, not the lookup itself, e.g. \"comparing admin tools for a two-location DPC clinic\", under 200 characters. No names or personal details. Omit it when you do not know; never invent one.",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "https://json-schema.org/draft/2020-12/schema",
-  "additionalProperties": false,
-  "properties": {
-    "id": {
-      "type": "string"
-    },
-    "text": {
-      "type": "string"
-    },
-    "title": {
-      "type": "string"
-    },
-    "url": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "id",
-    "title",
-    "text",
-    "url"
-  ],
-  "type": "object"
-}New value: +null
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false, destructiveHint=false), so the bar is lower. The description still adds real context beyond them: it discloses the return payload shape (one JSON text item with id, title, text, url) and the special side resources it can read. No auth or rate-limit detail, but that is a minor omission.

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?

Three dense sentences with no filler; the core capability and the id format are front-loaded before the special-file and return-shape details. Slightly compressed phrasing ('Answers one JSON text item') costs a little readability but nothing is wasted.

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?

With no output schema, the description correctly takes on the burden of describing the return payload (id, title, text, url). Combined with the id-format detail, an agent has enough to call it correctly; only the unresolved overlap with get_page keeps this short of complete.

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 50%: the optional 'intent' parameter is fully documented in the schema, but 'id' has no schema description at all. The description compensates by defining exactly what id accepts (a site path such as /pricing, or a URL carried by a search result), which is the meaningful semantic gap.

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 and resource: fetch the full markdown of a tabflows.com page, with the accepted id forms spelled out (/pricing-style path or a URL from a search result). The purpose is unambiguous, but it never addresses the overlapping sibling get_page, so an agent cannot tell from the description alone which of the two page-reading tools to pick.

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?

Usage is only implied: 'the URL a search result carries' hints that this follows a search call, and the llms.txt/sitemap.md mention hints at doc-retrieval use. There is no explicit when-to-use statement, no exclusions, and no routing against get_page, which appears to serve a near-identical need.

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

All Tabflows toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources