Skip to main content
Glama
yogeshkulkarni553

Content Server

searchOrganizationContents

Search through your organization's content database using semantic queries to find relevant information quickly.

Instructions

Search through the organization's content database using semantic search

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe search query

Implementation Reference

  • The handler function implementing the tool logic, performing semantic search via RagService.
    def search_organization_contents(self, query: str) -> list[str]:
        """
        Search through the organization's content database using semantic search.
    
        Args:
            query: The search query (required)
    
        Returns:
            List of search results
        """
        return self.rag_service.search_contents(query, self.user_id_from_environment)
  • Input schema defining the required 'query' parameter for the tool.
    inputSchema={
        "type": "object",
        "properties": {
            "query": {
                "type": "string",
                "description": "The search query"
            }
        },
        "required": ["query"],
        "additionalProperties": False
    }
  • mcp_server.py:58-72 (registration)
    Registers the tool in the MCP server's list_tools handler with name, description, and schema.
    types.Tool(
        name="searchOrganizationContents",
        description="Search through the organization's content database using semantic search",
        inputSchema={
            "type": "object",
            "properties": {
                "query": {
                    "type": "string",
                    "description": "The search query"
                }
            },
            "required": ["query"],
            "additionalProperties": False
        }
    ),
  • mcp_server.py:150-155 (registration)
    Handles tool calls by dispatching to the rag_tools.search_organization_contents method.
    elif name == "searchOrganizationContents":
        if "query" not in arguments:
            raise ValueError("Query parameter is required")
        result = rag_tools.search_organization_contents(arguments["query"])
        logger.debug(f"Tool {name} executed successfully")
        return [types.TextContent(type="text", text=str(result))]
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. It mentions 'semantic search' which adds some behavioral context beyond basic search, but doesn't disclose critical traits like whether this is read-only (likely, but not stated), what permissions are needed, rate limits, pagination behavior, or what the search covers (e.g., metadata, full text). For a search tool with zero annotation coverage, this is inadequate.

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 a single, efficient sentence that front-loads the core purpose. There's no wasted text, but it could be slightly more structured by explicitly mentioning the tool's scope or constraints.

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, no output schema, and a simple input schema, the description is incomplete. It lacks information on behavioral traits (e.g., safety, performance), output format (what results look like), and usage context relative to siblings. For a search tool in an organization content system, this leaves significant gaps for an AI agent.

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% (the single parameter 'query' is documented in the schema as 'The search query'), so the baseline is 3. The description adds no additional meaning about the parameter beyond what the schema provides—it doesn't explain query format, length limits, or how semantic search interprets the query.

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 action ('search through') and resource ('organization's content database') with the method 'using semantic search'. It distinguishes from siblings like listContentNames (listing names only) and upload tools (adding content). However, it doesn't explicitly contrast with deleteOrganizationContent.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies searching content, but doesn't specify when to prefer this over listContentNames for browsing or when semantic search is appropriate versus other search methods. No exclusions or prerequisites are mentioned.

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/yogeshkulkarni553/rag-mcp-py'

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