Skip to main content
Glama

search_in_project

Search within a Document360 project version to find specific articles or categories using a project version ID. This tool helps locate relevant knowledge base content by querying the project's search endpoint.

Instructions

Search inside a project version and return related articles/categories in Document360

Args: project_version_id: Document360 project version ID (UUID string) ctx: MCP context for logging and error handling

Returns: List of hits (articles/categories) from the project version search endpoint

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_version_idYesDocument360 project version ID (UUID string)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler implementation for the search_in_project tool. Performs search in Document360 project version using the client API, extracts hits, logs via ctx, and handles errors.
    async def search_in_project(project_version_id: str, ctx: Context) -> Dict[str, Any]:
        """Search inside a project version and return hits
    
        Args:
            project_version_id: Document360 project version ID (UUID string)
            ctx: MCP context for logging and error handling
    
        Returns:
            The raw response from /v2/ProjectVersions/{projectVersionId}/{langCode}, typically contains 'data.hits'
        """
        try:
            await ctx.info(f"Searching in project version: {project_version_id}")
    
            result = await client.search_project_version(project_version_id)
    
            hits = result.get('data', {}).get('hits', [])
    
            await ctx.info(f"Found {len(hits)} hits in project version {project_version_id}")
            return {'data': hits, 'success': True}
    
        except Document360APIError as e:
            await ctx.error(f"Document360 API error during project search: {e.message}")
            raise e
        except Exception as e:
            await ctx.error(f"Unexpected error during project search: {str(e)}")
            raise e
  • server.py:74-88 (registration)
    MCP tool registration for search_in_project, including schema definitions via Annotated types and Field descriptions, and docstring. Delegates to the core implementation in tools.py.
    @mcp.tool
    async def search_in_project(
        project_version_id: Annotated[str, Field(description="Document360 project version ID (UUID string)")],
        ctx: Context
    ) -> dict:
        """Search inside a project version and return related articles/categories in Document360
    
        Args:
            project_version_id: Document360 project version ID (UUID string)
            ctx: MCP context for logging and error handling
    
        Returns:
            List of hits (articles/categories) from the project version search endpoint
        """
        return await tools.search_in_project(project_version_id, ctx)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions returning a list of hits but doesn't describe key behaviors like pagination, error handling (beyond noting 'ctx' for logging), search scope (e.g., full-text, metadata), or performance considerations. The description is minimal and lacks 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 front-loaded with the core purpose, followed by structured sections for args and returns. It's efficient with minimal waste, though the 'ctx' parameter mention in args is redundant since it's not in the input schema and adds slight noise. Overall, it's well-structured and concise.

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 moderate complexity (search operation with one parameter), no annotations, and an output schema present (which covers return values), the description is minimally adequate. It states what the tool does and the return type but lacks context on usage, behavioral details, and integration with siblings. It meets basic requirements but has clear gaps.

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%, with the parameter 'project_version_id' documented as a UUID string. The description adds no additional semantic context beyond what the schema provides (e.g., how to obtain this ID, format examples, or validation rules). Baseline score of 3 is appropriate since the schema handles parameter documentation adequately.

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: 'Search inside a project version and return related articles/categories in Document360.' It specifies the verb (search), resource (project version), and target (articles/categories). However, it doesn't explicitly differentiate from sibling tools like 'list_project_versions' or 'get_article' in terms of search vs. retrieval operations.

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 sibling tools like 'get_article' for direct retrieval or 'list_project_versions' for listing versions, nor does it specify prerequisites such as needing a valid project version ID from another tool. Usage is implied but not explicitly stated.

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