Skip to main content
Glama
Sign In
hermes-gpt

hermes-gpt

by n0geegee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

hermes_read_file

Read-onlyIdempotent

Read a local file from the Hermes machine by providing an explicit file path. Supports optional offset and limit for partial reads.

Instructions

Read a local file from this Hermes machine. Use only when the user provides an explicit path.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "hermes_read_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
offsetNo
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already indicate readOnly, destructive, idempotent. Description adds no additional behavioral traits (e.g., pagination via offset/limit, error handling, permission requirements).

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 sentences, each essential. First states purpose, second adds a critical usage condition. No fluff.

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

Completeness2/5

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

Despite existing output schema, description omits parameter meanings (especially offset/limit), error scenarios, and path requirements. Minimal for a tool with 3 parameters.

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

Parameters1/5

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

With 0% schema description coverage, description must explain parameters. It does not mention path, offset, or limit at all, leaving the agent with no guidance 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?

'Read a local file' is a specific verb+resource. The condition 'use only when the user provides an explicit path' distinguishes it from sibling tools that list or search files.

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?

Clear condition to use only when user provides explicit path. Does not name alternatives like hermes_list_files, but condition is explicit enough to guide selection.

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