Skip to main content
Glama
Sign In
keystone-mcp

keystone-mcp

by tacoda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

keystone_list_topics

Retrieve a list of configured topics from company resources. Pass a tag to filter topics and locate relevant rules, reasoning, skills, and commands.

Instructions

List configured topics. Pass tag to filter.

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

Input Schema

NameRequiredDescriptionDefault
tagNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

There are no annotations, so the description carries the full burden. It clearly states the action (list) and the scope (configured topics), implying a read-only operation, and mentions the filtering behavior. However, it does not disclose behaviors like tag matching semantics, ordering, pagination, or potential errors.

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 two short sentences, front-loaded with the core purpose and no superfluous words. Every part earns its place.

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?

Given the tool's simplicity (one optional parameter, an output schema present), the description covers the essential use case. It lacks richer context around filter semantics and when to select this tool, but that is a minor gap for a straightforward list operation.

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 has 0% description coverage, so the description must compensate for the sole parameter. It does add meaning by stating the tag is used to filter, which is not in the schema. Yet it leaves details ambiguous, such as whether the filter is an exact match or substring, limiting full semantic clarity.

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 uses a specific verb ('List') and a concrete resource ('configured topics'), and immediately distinguishes itself from the sibling creation tools (e.g., keystone_new_*). The mention of the optional tag filter further refines the 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 exclusions or prerequisites. The only usage hint is 'Pass `tag` to filter', which is a parameter instruction, not a when-to-use guideline.

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