Skip to main content
Glama

ultrathink_search

Search the Ultrathink knowledge base with natural language queries to get AI-generated answers based on stored entries.

Instructions

Search the Ultrathink knowledge base using natural language. Returns an AI-generated answer based on stored entries.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "ultrathink_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesNatural language search query
entityFilterNoOptional filter by entity type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the important trait that results are AI-generated answers derived from stored entries rather than literal matches. It says nothing about read-only safety, latency/cost of generation, empty-result behavior, or whether source entries are cited.

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?

Two sentences, zero waste, with the core action front-loaded and the return behavior immediately after. Nothing in it is redundant.

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?

There is no output schema, so the description must characterize the return value, and it does so only in one broad clause. For a simple two-parameter read tool this is close, but the answer shape (citations, multiple entries, result limits) remains undefined.

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 both parameters and the enum values documented inline, so the baseline is 3. The description adds no meaning beyond the schema for query or entityFilter, such as expected phrasing or what happens when the filter is omitted.

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 names a specific verb (Search) and resource (the Ultrathink knowledge base) and clarifies that the output is a synthesized answer rather than raw records. That distinguishes it well from the only sibling, ultrathink_save, though the contrast is never stated explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the retrieval path versus ultrathink_save for storage, and that entityFilter narrows scope. There is no explicit when-to-use, when-not-to-use, or guidance on choosing between filtered and unfiltered searches.

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