penelope-mcp

Official

Overview Schema Source Related Servers Discussions Admin

browse_topics

List the immediate children of a telemetry topic namespace to explore its hierarchy. Use this to navigate nested topic folders and identify where topics exist before descending further.

Instructions

List the immediate children of a topic namespace, like ls.

Use this to explore, and search_topics to find. Topic names are deeply nested -- most are six segments -- so a namespace can hold hundreds of topics while having only a handful of children. BMS/PerCell holds 970 of 25A's 1502 topics but has exactly two children, Alpha and Beta. Searching that prefix returns an unreadable page of leaf names; browsing it returns two lines.

Call with no prefix for the top-level namespaces, then walk down. Each child reports topics (how many exist at or below it), so you can see where the mass is before descending, and is_topic (whether the path is itself a logged topic rather than only a folder).

Once you reach a specific topic, confirm it with describe_topic.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`car`	No
`limit`	No
`prefix`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure. It explains that the tool lists only immediate children (not recursive), that namespaces can hold many topics but few children, and that each child reports `topics` and `is_topic`. It does not mention pagination or `limit` behavior, which is a minor gap.

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 front-loaded with the core behavior and uses a concrete, vivid example (BMS/PerCell) to illustrate why browsing beats searching on nested namespaces. Every sentence earns its place by defining behavior, giving usage guidance, or explaining output semantics.

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?

The output schema exists, and the description covers the browsing workflow, result field semantics, and follow-up action. The main gap is the undocumented `car` and `limit` parameters; otherwise the tool is well contextualized for an agent.

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%, so the description must compensate. It thoroughly explains `prefix` (no prefix means top-level, then walk down), but says nothing about `limit` or the opaque `car` parameter. With three undocumented parameters and one non-obvious parameter, this is insufficient.

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 opening sentence names a specific verb and resource ('List the immediate children of a topic namespace') and the `ls` analogy makes the behavior instantly recognizable. It is explicitly contrasted with `search_topics` and `describe_topic`, so an agent can tell it apart from its siblings.

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

Usage Guidelines5/5

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

The description states 'Use this to explore, and search_topics to find' and gives a concrete workflow: call with no prefix for top-level namespaces, walk down, then confirm with describe_topic. This is explicit when-to-use guidance with named alternatives.

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

Deploy Server