Skip to main content
Glama
Melbourneandrew

docs2prompt MCP Server

get_url_docs

Retrieves documentation from a specified URL for extracting LLM-friendly prompts.

Instructions

Use this tool to get the documentation at a URL.

Args:
    url: The URL to get the documentation for.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes

Implementation Reference

  • The tool handler function 'get_url_docs' takes a URL and calls get_url_documentation from the docs2prompt library.
    @mcp.tool()
    async def get_url_docs(url: str):
        """
        Use this tool to get the documentation at a URL.
    
        Args:
            url: The URL to get the documentation for.
        """
        return get_url_documentation(url)
  • The tool has one parameter 'url' of type str, defined by the function signature. The docstring serves as the schema description.
    @mcp.tool()
    async def get_url_docs(url: str):
        """
        Use this tool to get the documentation at a URL.
    
        Args:
            url: The URL to get the documentation for.
        """
  • src/main.py:27-27 (registration)
    The tool is registered via the @mcp.tool() decorator on the FastMCP instance 'mcp' (line 5).
    @mcp.tool()
  • The helper function 'get_url_documentation' is imported from the docs2prompt library and called by the handler.
    from docs2prompt import get_github_documentation, get_url_documentation
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the basic function, omitting any details about error handling, authentication, or side effects. For a simple tool, this is insufficient to fully inform an agent.

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?

The description is extremely concise with two sentences, front-loading the purpose. Every word earns its place, no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (1 param, no output schema), the description is minimally adequate. It explains what the tool does and the parameter, but lacks contextual guidance about when to prefer this tool over its sibling.

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?

The schema has 0% description coverage, so the description must compensate. It identifies the parameter as a URL, adding meaning beyond the bare schema. However, it does not specify URL format or constraints, providing minimal added value.

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?

The description clearly states the tool retrieves documentation from a URL, using specific verb+resource. However, it does not differentiate from the sibling tool 'get_docs2prompt_docs', so it loses a point for lack of distinction.

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 description tells when to use the tool ('get the documentation at a URL'), but provides no guidance on when not to use it or alternatives (e.g., the sibling tool). It is implied usage without exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Melbourneandrew/docs2prompt-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server