Skip to main content
Glama

search_tools

Query the tool graph using natural language to retrieve relevant tools, deprioritizing previously used ones to discover new options.

Instructions

Search for relevant tools by natural language query.

    Returns the most relevant tools for the given query, ranked by
    graph-based hybrid retrieval (BM25 + graph traversal + embedding).
    Previously called tools are automatically deprioritized to surface
    new candidates on repeated searches.

    Args:
        query: Natural language description of what you want to do.
               Examples: "user authentication", "delete a file",
               "manage shopping cart items"
        top_k: Maximum number of tools to return (default: 5)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
top_kNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses graph-based hybrid retrieval and deprioritization of previously called tools, adding value beyond missing annotations. Some details like error handling are omitted.

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?

Concise, front-loaded purpose, no filler, every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given output schema coverage and tool simplicity, the description covers retrieval method, ranking, and parameter hints sufficiently.

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

Parameters5/5

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

The Args section provides examples and default for query and top_k, compensating for 0% schema description coverage.

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 clearly states the tool searches for relevant tools by natural language query, specifies the retrieval method, and distinguishes from siblings like execute_tool or get_tool_schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when needing to find tools via natural language, but lacks explicit when-not-to-use or alternative tools, though context from sibling names makes it clear.

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/SonAIengine/graph-tool-call'

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