Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Metis — KG Community

kg_community

Find related notes in your knowledge graph by exploring connections up to a specified depth from a starting note.

Instructions

Return the connected cluster around a given knowledge library note.

Performs BFS flood-fill from the given note up to `depth` hops,
returning all reachable notes grouped by distance. Useful for surfacing
related concepts when working on a specific topic.

Args:
    note_path: Relative path from knowledge/library/ (e.g. 'disease-areas/[condition].md')
    depth:     Maximum hop distance to explore (default 2).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNo
note_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

No annotations exist, so the description carries full burden. It explains the BFS algorithm, depth parameter behavior, and output grouping by distance, but omits side effects or safety guarantees. This is sufficient for a read-only tool.

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 concise with a bold first line, followed by an algorithm explanation and clear parameter docs. Every sentence adds value with no redundancy.

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

Completeness5/5

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

Given the tool has an output schema (context signal) and only two simple parameters, the description fully covers behavior and parameter usage, making it complete for practical use.

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

Parameters5/5

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

Schema coverage is 0%, but the description provides comprehensive parameter documentation, including file path format and default depth value, adding essential meaning beyond the schema.

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 'Return the connected cluster around a given knowledge library note' with a specific verb and resource. It distinguishes from sibling tools like kg_paths and kg_memory_connections by its BFS flood-fill approach for community detection.

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

Usage Guidelines4/5

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

The description provides usage context ('Useful for surfacing related concepts when working on a specific topic') but does not explicitly state when not to use or mention alternative sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server