Skip to main content
Glama
Sign In

Tabflows

by com.tabflows
OverviewDiscussionsAdmin

Read a tabflows.com page

get_page
Read-only

The full markdown of any public tabflows.com page by path or URL, e.g. /pricing, /faqs, /compliance, /glossary, /dpc-finder/texas, and the index files /llms.txt, /llms-full.txt and /sitemap.md. Answers one JSON text item holding id, title, text and url.

Input Schema

NameRequiredDescriptionDefault
pathYes
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.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, non-destructive and openWorldHint=false; the description adds value beyond them by disclosing the 'public pages only' access restriction and the shape of the response ('one JSON text item holding id, title, text and url'). It does not say what happens on a private/nonexistent path, but the annotation bar is lower here.

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?

Two sentences, front-loaded with the core action, and every element (path examples, index files, return fields) carries information. The example list is dense but each item earns its place as format guidance.

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 covers the return payload (id, title, text, url) and the path format. For a simple read tool with strong annotations, the only minor gap is error/not-found behavior for non-public or invalid paths.

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 coverage is 50%: the intent parameter is fully documented in the schema, but path has no schema description. The description partially compensates by showing accepted path formats (leading-slash paths and index files), though 'by path or URL' is slightly looser than the schema's single string path field. 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+resource ('full markdown of any public tabflows.com page') and enumerates concrete path examples (/pricing, /faqs, /llms.txt) so the agent can distinguish it from siblings like fetch, search and list_integrations without opening the schema.

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?

The scope boundary ('any public tabflows.com page') and the example paths imply when the tool applies, but there is no explicit when-to-use guidance, no statement of when NOT to use it, and no routing to alternatives such as search for discovering pages or fetch for non-tabflows content.

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