Skip to main content
Glama

knowledge_search

Read-only

Search cached FiveM guides, native hashes, and installed KQ Link source by exact API name or technical phrase to locate relevant development references.

Instructions

Search cached guides, FiveM natives and installed KQ Link source. Use an exact API name, native hash or technical phrase.

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": "knowledge_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
queryYes
apiSetNo
sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered. The description adds that results come from a *cache* (implying possible staleness) and are scoped to *installed* KQ Link source. It says nothing about result ranking, truncation at the limit, or what a hit looks like, so its added behavioral value is modest.

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?

Two sentences, zero filler, with the resource scope front-loaded and the query-format hint immediately after. Efficient for the space, though it spends no words on the filters that most need explanation.

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

Completeness4/5

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

For a read-only search over three corpora, the definition tells an agent what is searched and how to phrase the query, which is sufficient to attempt a correct first call. Missing: how results are ranked/truncated, whether `kind` is required for unscoped searches, and what `apiSet`/`source` do — details an agent would otherwise have to guess.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters. The description adds meaning only for `query` (exact API name, native hash, or technical phrase) and hints at the corpora behind `kind`, but says nothing about `apiSet` (client/server/shared), `source` (framework enum), or `limit` (default 5, max 10). With four of five parameters undocumented anywhere, the description fails to compensate for the coverage gap.

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 concrete verb ("Search") and enumerates the corpora searched: cached guides, FiveM natives, and installed KQ Link source. That is enough to separate it from knowledge_read (which implies fetching a specific item) and knowledge_sources, though the boundary is only implied rather than stated.

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?

It advises how to phrase the query — "an exact API name, native hash or technical phrase" — which implies an exact/near-exact lookup rather than a broad exploratory search. It gives no when-to-use versus knowledge_read or knowledge_sources, and no when-not-to-use or fallback guidance.

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