Skip to main content
Glama

query_entities

Search and filter entities (classes, functions, modules) in a knowledge graph by type, programming language, or name pattern using customizable parameters for precise results.

Instructions

Query entities in the knowledge graph.

Args: entity_type: Filter by entity type (class, function, module, etc.) language: Filter by programming language name_pattern: Filter by name pattern (regex) limit: Maximum number of results to return

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_typeNo
languageNo
limitNo
name_patternNo

Implementation Reference

  • MCP tool handler for 'query_entities'. This is the main execution function, decorated with @self.mcp.tool() which registers it as an MCP tool. It calls KnowledgeGraph.query_entities and formats the results as a string.
    @self.mcp.tool()
    def query_entities(
        entity_type: str | None = None,
        language: str | None = None,
        name_pattern: str | None = None,
        limit: int = 10,
    ) -> str:
        """Query entities in the knowledge graph.
    
        Args:
            entity_type: Filter by entity type (class, function, module, etc.)
            language: Filter by programming language
            name_pattern: Filter by name pattern (regex)
            limit: Maximum number of results to return
        """
        entities = self.knowledge.query_entities(
            entity_type=entity_type,
            language=language,
            name_pattern=name_pattern,
            limit=limit,
        )
    
        if not entities:
            return "No entities found matching the query criteria"
    
        # Format results
        output = f"Found {len(entities)} entities:\n\n"
    
        for entity in entities:
            output += f"Name: {entity.name}\n"
            output += f"Type: {entity.entity_type}\n"
    
            if entity.language:
                output += f"Language: {entity.language}\n"
    
            if entity.signature:
                output += f"Signature: {entity.signature}\n"
    
            output += f"Summary: {entity.summary}\n"
    
            if entity.observations:
                output += "Observations:\n"
                for observation in entity.observations[
                    :3
                ]:  # Limit to 3 observations
                    output += f"- {observation}\n"
    
                if len(entity.observations) > 3:
                    output += f"... and {len(entity.observations) - 3} more observations\n"
    
            output += "\n"
    
        return output
  • Core implementation of entity querying in KnowledgeGraph class. Filters entities by type, language, and name pattern using regex, with optional limit.
    def query_entities(
        self,
        entity_type: str | None = None,
        language: str | None = None,
        name_pattern: str | None = None,
        limit: int = 100,
    ) -> list[Entity]:
        """Query entities based on criteria.
    
        Args:
            entity_type: Filter by entity type
            language: Filter by programming language
            name_pattern: Filter by name pattern (regex)
            limit: Maximum number of results
    
        Returns:
            List of matching entities
        """
        results = []
    
        for entity in self.entities.values():
            # Apply filters
            if entity_type is not None and entity.entity_type != entity_type:
                continue
    
            if language is not None and entity.language != language:
                continue
    
            if name_pattern is not None:
                if not re.search(name_pattern, entity.name):
                    continue
    
            results.append(entity)
    
            if len(results) >= limit:
                break
    
        return results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose any behavioral traits such as side effects, read-only status, pagination, or output format. It only describes filters.

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 very concise, using a structured list format for parameters with no superfluous text. Every sentence serves a purpose.

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?

No output schema and no annotation context. The description fails to explain what the tool returns, any sorting or pagination, or edge case behavior, leaving the agent with insufficient information.

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?

With 0% schema description coverage, the description adds meaningful semantics by explaining each parameter (entity type, language, regex pattern, limit). However, it lacks examples or further detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states 'Query entities in the knowledge graph', which is a clear verb-resource pair. It distinguishes from sibling query tools like query_patterns and query_style_conventions by specifying entities.

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 guidance on when to use this tool versus alternatives. The description only lists parameters without any context about use cases, prerequisites, or when not to use it.

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

Deploy Server

Other Tools

Related Tools