Skip to main content
Glama

search_knowledge_graph

Search a knowledge graph using natural language or exact terms to find entities and relationships. Use semantic search for conceptual queries or basic matching for precise results.

Instructions

Search the knowledge graph using semantic or basic search

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repository_pathYesThe absolute path to the repository to search within
queryYesThe search query text. Can be natural language for semantic search or specific terms for exact matching
entity_typesNoOptional array of entity types to filter the search results. If not provided, all entity types will be searched
relationship_typesNoOptional array of relationship types to filter relationships in the results. If not provided, all relationship types will be included
use_semantic_searchNoWhether to use semantic vector search (true) or basic text matching (false). Semantic search is more powerful for finding conceptually related entities
include_relationshipsNoWhether to include relationships between entities in the search results. Set to false for faster queries when only entities are needed
limitNoMaximum number of results to return (1-100)
thresholdNoSimilarity threshold for semantic search results (0.0 to 1.0, where 1.0 requires exact matches)
Behavior2/5

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

No annotations provided, so description carries full burden. It does not disclose behavioral traits like performance characteristics, result format, or idempotency. For a search tool, it's acceptable but lacks detail.

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?

One clear sentence without fluff. It is front-loaded with the core action. Could be slightly more concise, but efficient.

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?

For a search tool with 8 parameters and no output schema, the description does not explain the return format or pagination behavior (though limit is in schema). It covers the purpose but not the full user experience.

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 coverage is 100% with detailed parameter descriptions. The tool's description adds little beyond what the schema already provides (e.g., semantic vs. basic search is already in use_semantic_search). Baseline 3 is appropriate.

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) and the resource (knowledge graph), and mentions two search modes (semantic or basic). This differentiates it from sibling tools like find_related_entities or store_knowledge_memory.

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 vs. alternatives (e.g., find_related_entities). The description does not mention prerequisites, limitations, or preferred scenarios.

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/ZachHandley/ZMCPTools'

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