Skip to main content
Glama
cdmx-in
by cdmx-in

get_document_content

Retrieve document content from Goodday project management using the document ID to access specific files for reference or analysis.

Instructions

Get the content of a specific document by its ID.

Args: document_id: The ID of the document to retrieve

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
document_idYes

Implementation Reference

  • The handler and registration for the 'get_document_content' tool. Decorated with @mcp.tool(), it fetches document content from Goodday API endpoint 'document/{document_id}' using the shared make_goodday_request helper, handles errors, extracts content, and formats the response.
    async def get_document_content(document_id: str) -> str:
        """Get the content of a specific document by its ID.
    
        Args:
            document_id: The ID of the document to retrieve
        """
        data = await make_goodday_request(f"document/{document_id}")
    
        if not data:
            return "Document not found or no content available."
    
        if isinstance(data, dict) and "error" in data:
            return f"Unable to fetch document: {data.get('error', 'Unknown error')}"
    
        if isinstance(data, dict):
            content = data.get('content', data.get('text', str(data)))
        else:
            content = str(data)
    
        return f"**Document Content:**\n\n{content}"
Behavior2/5

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

No annotations are provided, so the description carries full burden but offers minimal behavioral insight. It states it 'retrieves' content, implying a read-only operation, but doesn't cover permissions, rate limits, error handling, or output format (e.g., text, binary, structured data). This is inadequate for a tool with no annotation coverage.

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?

The description is front-loaded with the core purpose in the first sentence, followed by a brief parameter explanation. It avoids redundancy and is appropriately sized for a simple tool, though the 'Args:' section could be integrated more smoothly.

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

Completeness2/5

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

Given no annotations, 0% schema coverage, and no output schema, the description is insufficient. It doesn't explain what 'content' means (e.g., full text, attachments), potential side effects, or how results are returned, making it hard for an agent to use correctly without trial and error.

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 description adds basic meaning by explaining that 'document_id' identifies the document to retrieve, which is helpful since schema description coverage is 0%. However, it doesn't specify the ID format (e.g., numeric, UUID) or where to find it, leaving gaps despite the single parameter.

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's purpose with a specific verb ('Get') and resource ('content of a specific document'), making it immediately understandable. However, it doesn't differentiate from sibling tools like 'search_project_documents' or 'get_task_details', which might also retrieve document-related content in different contexts.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'search_project_documents' and 'get_task_details', it's unclear if this is for raw document content, metadata, or specific contexts, leaving the agent to guess based on tool names alone.

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/cdmx-in/goodday-mcp'

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