Skip to main content
Glama

list_project_versions

Retrieve all available project versions from Document360 to access specific documentation sets for browsing, searching, or reading articles.

Instructions

List all project versions from Document360

Args: ctx: MCP context for logging and error handling

Returns: List of project versions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that lists project versions using the Document360 client, includes logging and comprehensive error handling.
    async def list_project_versions(ctx: Context) -> Dict[str, Any]:
        """List all project versions from Document360
        
        Args:
            ctx: MCP context for logging and error handling
            
        Returns:
            List of project versions from Document360 API
        """
        try:
            await ctx.info("Listing all project versions")
            result = await client.list_project_versions()
            await ctx.info(f"Found {len(result.get('data', []))} project versions")
            return result
        except Document360APIError as e:
            await ctx.error(f"Document360 API error: {e.message}")
            raise e
        except Exception as e:
            await ctx.error(f"Unexpected error listing project versions: {str(e)}")
            raise e
  • server.py:106-116 (registration)
    MCP tool registration using @mcp.tool decorator. Defines input/output schema via type hints and docstring. Delegates execution to the tools module.
    @mcp.tool
    async def list_project_versions(ctx: Context) -> dict:
        """List all project versions from Document360
    
        Args:
            ctx: MCP context for logging and error handling
    
        Returns:
            List of project versions
        """
        return await tools.list_project_versions(ctx)
  • Low-level helper in Document360Client that performs the HTTP GET request to the /v2/ProjectVersions endpoint to fetch the list of project versions.
    async def list_project_versions(self) -> Dict[str, Any]:
        """Get list of all project versions"""
        return await self._request("GET", "/ProjectVersions")
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it 'List all project versions' which implies a read-only operation, but doesn't mention any behavioral traits like pagination, rate limits, authentication requirements, or what happens if no versions exist. The description is minimal and lacks important operational context.

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 appropriately concise with a clear purpose statement followed by Args and Returns sections. However, the Args section mentions 'ctx' which isn't in the input schema, creating minor confusion. The structure is good but could be slightly cleaner by omitting the unnecessary ctx reference.

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 has no parameters, an output schema exists, and annotations are absent, the description is minimally adequate. It states what the tool does and what it returns, but lacks context about when to use it, behavioral constraints, or how it relates to sibling tools. The presence of an output schema means it doesn't need to explain return values, but other gaps remain.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of parameters. The description correctly notes there are no arguments beyond the context parameter (ctx), which aligns with the empty schema. This meets the baseline expectation for parameterless tools.

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 verb 'List' and resource 'project versions from Document360', making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'search_in_project' which might also retrieve project-related data, so it doesn't achieve full sibling differentiation.

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. It doesn't mention whether this is for retrieving all versions versus filtered versions, or how it differs from sibling tools like 'search_in_project'. No context or exclusions are provided.

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/druellan/document360-mcp'

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