Skip to main content
Glama
Sign In
agent-knowledge

agent-knowledge

by yucx-go
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ak_query

Search the agent-knowledge vault to retrieve relevant information from its structured knowledge base. Submit a query to get the top matching results.

Instructions

Search the knowledge vault for relevant information.

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

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query text.
top_kNoMaximum number of results to return (default: 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'search', which implies read-only behavior, but does not explicitly state that it is non-destructive, nor does it mention return format, ranking, or any side effects. This is minimal transparency.

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 a single, clear sentence with no filler words. It is appropriately front-loaded and concise, containing only the essential information.

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?

The tool is simple with well-documented parameters, but there is no output schema, and the description does not describe what the search returns or how results are presented. This is a noticeable gap for a query tool, though the core functionality is clear.

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?

The schema already documents both parameters ('query' and 'top_k') with 100% coverage, so the description adds no additional parameter meaning. A baseline score of 3 is appropriate since the schema handles parameter semantics.

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 action ('Search') and the resource ('the knowledge vault'), making it specific and distinct from sibling tools like ak_ingest and ak_stats. It unambiguously conveys the tool's purpose.

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?

The description provides no guidance on when to use this tool versus alternatives, nor any explicit exclusions or prerequisites. It simply states the action without contextual usage direction.

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