Skip to main content
Glama
Sign In
hermes-gpt

hermes-gpt

by n0geegee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

hermes_tree

Read-onlyIdempotent

Display a shallow directory tree of an allowed local path for safe, read-only file discovery.

Instructions

Show a shallow directory tree for an allowed local path. Read-only and safer than regex search for discovery.

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

Input Schema

NameRequiredDescriptionDefault
pathNo.
depthNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Adds 'read-only' and 'safer' beyond annotations (which already mark readOnlyHint=true and destructiveHint=false), reinforcing behavior without contradiction.

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?

Two front-loaded sentences deliver purpose and key attribute concisely, with no unnecessary 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?

Simple tool with output schema and annotations; description covers core purpose but omits parameter details, which are essential for usage completeness.

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?

No parameter descriptions in schema or description; 'shallow' hints at depth but does not explain path, depth, or limit semantics, failing to compensate for 0% schema coverage.

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?

Description uses specific verb 'show' and resource 'shallow directory tree', clearly distinguishing from sibling tools like regex-based search.

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?

Suggests use for discovery over regex search; implies read-only nature. No explicit when-not-to-use, but context with sibling names provides guidance.

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