TechFabric

Explore a post

explore_post

Read-onlyIdempotent

Interactive: walk through a published techfabric.com post or case study: its diagram (the Mermaid flowchart it publishes) as steps in the order it flows, each step tied to the section it's about, with that section's opening in the page's own words and a link to it. A page with no diagram steps through its sections. Takes a URL, a slug or a topic (the closest post or case study). In a host that renders MCP Apps it opens as a view to click through; the text is complete without it. For example: "walk me through this post step by step", "show me how this works", "explain the diagram in this case study".

Input Schema

Name	Required	Description	Default
`post`	Yes	A post or case study: its URL, path or slug (case studies as case-studies/<slug>), or the topic to find one on
`diagram`	No	Which of its diagrams, when it has more than one (default 1)

Output Schema

Name	Required	Description
`kind`	Yes
`mode`	Yes	diagram: the steps are its Mermaid diagram's nodes; sections: it has no diagram, and the steps are its sections
`note`	Yes
`page`	Yes
`asked`	Yes
`steps`	Yes
`diagram`	Yes
`diagrams`	Yes
`sections`	Yes
`faq_count`	Yes
`alternatives`	Yes
`resolved_from`	Yes
`quiz_questions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026

addedOutput schema / properties / quiz_questions
```
Added value: +{
+  "type": "integer"
+}
```

changedOutput schema / required

Previous value: -[
-  "kind",
-  "asked",
-  "resolved_from",
-  "page",
-  "mode",
-  "diagram",
-  "diagrams",
-  "steps",
-  "sections",
-  "faq_count",
-  "alternatives",
-  "note"
-]New value: +[
+  "kind",
+  "asked",
+  "resolved_from",
+  "page",
+  "mode",
+  "diagram",
+  "diagrams",
+  "steps",
+  "sections",
+  "faq_count",
+  "quiz_questions",
+  "alternatives",
+  "note"
+]

Changed2 schema fields changedOct 24, 2026

addedOutput schema / properties / steps / items / properties / headline

Added value: +{
+  "description": "The step's title for a reader: the post's own short sentence about the node, or the label's lead",
+  "type": "string"
+}

addedOutput schema / properties / steps / items / properties / title / description
```
Added value: +"The diagram node's label (or the section's heading)"
```

AddedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: the diagram becomes click-through steps, pages without a diagram fall back to section stepping, topic input resolves to the closest post, and the text output is complete without an MCP Apps host. It doesn't mention limits on which posts are explorable or how much of the section body is returned.

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?

Front-loads the core definition, then host behavior, then example phrasings, in that order. Despite covering several topics the prose is dense and every clause carries information; nothing is repeated from the title or schema.

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, return values need no explanation, and the description still covers the interactive rendering caveat, the no-diagram fallback, and input resolution. Nothing an agent needs to invoke this correctly is missing.

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%, so both parameters are already documented, and the description largely restates the same accepted inputs. The one additive detail is the parenthetical '(the closest post or case study)', which clarifies topic resolution is nearest-match rather than exact, but that is a marginal gain over the schema text.

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?

Names a specific verb ('walk through') and a precise resource ('a published techfabric.com post or case study'), then defines the output shape: diagram steps in flow order, each tied to its section with that section's opening text and a link. The 'interactive walkthrough of a published page' framing cleanly separates it from sibling write/lint tools and from plain page retrieval like get_page or preview_diagram.

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 the accepted input forms (URL, slug, or topic) and concrete trigger phrasings ('walk me through this post step by step', 'explain the diagram in this case study'), which tells the agent the user intents this tool serves. It does not name alternatives or state when another sibling should be used instead, so it stops short of full when/when-not routing.

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

All TechFabric 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.