Tabflows

Search tabflows.com

search

Read-only

Keyword search over tabflows.com pages (product, pricing, FAQs, compliance, glossary, blog, integrations). Each result carries a page id, its title, a snippet of the text that matched and its URL; fetch reads the full page by that id or URL. DPC Finder listings are not indexed here; search_dpc_practices covers them.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes
`intent`	No	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.

Output Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

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."

Changed1 schema field changedOct 13, 2026

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"
+}

Changed2 schema fields changedOct 13, 2026
- addedOutput schema / properties / results / items / properties / snippet
```
Added value: +{
+  "type": "string"
+}
```
- changedOutput schema / properties / results / items / required
```
Previous value: -[
-  "id",
-  "title",
-  "url"
-]New value: +[
+  "id",
+  "title",
+  "snippet",
+  "url"
+]
```
First observedSep 16, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the exact index coverage (product, pricing, FAQs, compliance, glossary, blog, integrations) and the explicit exclusion of DPC Finder listings.

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, front-loaded with the core purpose and index scope, then the result shape, then the exclusion and alternative. Every clause carries distinct information with no padding.

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?

With an output schema present, the description correctly needn't re-explain return values, and with annotations present the safety profile is covered. What remains — index scope, the id/URL hand-off to `fetch`, and the search_dpc_practices alternative — is exactly the routing information an agent needs.

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 richly documented in the schema itself, while `query` carries no description but is self-evident from its name and constraints. The description adds no syntax, format or length guidance beyond what the schema already provides, so the baseline 3 applies.

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 ('Keyword search') and a precisely bounded resource ('tabflows.com pages') and enumerates the page families covered. It also explicitly differentiates itself from the sibling search_dpc_practices by naming what is absent from the index.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-not guidance ('DPC Finder listings are not indexed here; search_dpc_practices covers them') and routes the agent onward to `fetch` for full page content by id or URL. The agent can choose between search, search_dpc_practices and fetch without opening any schema.

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

All Tabflows tools Inspect

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

Need Help?