MintMCP Docs

Fetch a MintMCP docs page

fetch

Read-onlyIdempotent

Fetch the full markdown content of a MintMCP documentation page by its id. Use it after search (or list_docs) to read a page in full before answering, for example the Snowflake connector setup, the SCIM provisioning guide, or the tool governance reference. If you have a public docs URL or a slug instead of a search-result id, use get_page.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	The document id returned by search or list_docs.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`text`	Yes
`title`	Yes
`metadata`	No

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare read-only and idempotent. Description adds that it returns 'full markdown content', specifying output format beyond annotations. No contradictions.

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, no fluff, main action first. Efficient.

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?

Covers input source and output format. With output schema present, no need for return value details. Could mention errors or rate limits, but adequate for simple tool.

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

Parameters5/5

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

Only one parameter with 100% schema coverage. Description adds meaning by stating the id comes from search or list_docs, which is not in schema.

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?

The description clearly states it fetches markdown content by document id, with specific verb+resource. It distinguishes from sibling tools by mentioning get_page for alternative input types.

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?

Explicitly says when to use (after search/list_docs) and when not to (when having URL/slug), providing alternatives (get_page).

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

All MintMCP Docs tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clear, distinct purpose: two fetch variants (by id vs by URL), one for listing the table of contents, and one for searching. No overlap or ambiguity.

Naming Consistency5/5

All tool names use lowercase verb_noun pattern (fetch, get_page, list_docs, search), consistent and predictable.

Tool Count4/5

Four tools is on the minimal side but provides essential documentation operations: search, list, and two fetch methods. Slightly more could be added (e.g., get categories) but the set is not insufficient.

Completeness4/5

The tool surface covers the main use cases: discovering docs, searching, and retrieving content. No major gaps, though a tool to list only categories or tags could enhance exploration.

Resources

Need Help?