Skip to main content
Glama
Sign In
Kilonova MCP

Kilonova MCP

by MilnaOS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

kb_topics

Lists all available knowledge base topics and their entity type counts so you can discover stored project context and choose which topics to inspect.

Instructions

List all available KB topics and their entity type counts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kb_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose the return content (topic names plus entity type counts), which is the main behavioral fact an agent needs, and "List" implies a safe read. However, it says nothing about ordering, whether results are paginated, or whether it requires an initialized KB, which a zero-annotation tool ideally would cover.

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?

A single sentence with zero waste, front-loaded with the verb and the resource and followed immediately by the payload detail. Nothing could be cut without losing information.

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 parameterless listing tool with no output schema and no annotations, the description supplies the essential purpose and the content of each item. The only shortfall is the absence of routing guidance among the seven sibling tools, which matters more here than for a highly differentiated tool.

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

Parameters4/5

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

The tool takes no parameters, so the schema is trivially complete and there is nothing for the description to disambiguate. The baseline of 4 applies for a zero-parameter tool.

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?

"List" is a specific verb applied to a specific resource (KB topics), and the description additionally states what each entry contains (entity type counts). That makes the tool's output shape distinguishable from kb_search or kb_schema, though it never explicitly names or contrasts those siblings.

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?

There is no explicit statement of when to reach for this tool versus kb_schema, corpus_status, or kb_search. "List all available" hints at a discovery/browsing use case, but the agent must infer that on its own, and no exclusions or prerequisites are given.

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