Skip to main content
Glama
Perseus-Computing-LLC

perseus

by Perseus-Computing-LLC
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

perseus_read

Read-only

Read file contents and embed them into context. Extract specific keys from structured files or validate against JSON schemas.

Instructions

Read and embed file contents into the rendered context. Use to inject config values, environment files, or any text file. Can extract specific keys from structured files. Read-only; use perseus_list or perseus_tree to browse before reading.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoIf reading a config file, extract this key only
pathYesFile path to read (relative to workspace root)
schemaNoJSON Schema to validate file contents against
fallbackNoValue to use when the file or key is not found

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoFile path read
contentNoFile contents
truncatedNoWhether content was truncated

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.0.10
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "content": {
+      "description": "File contents",
+      "type": "string"
+    },
+    "path": {
+      "description": "File path read",
+      "type": "string"
+    },
+    "truncated": {
+      "description": "Whether content was truncated",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. Changed4 schema fields changedv1.0.7
    • changedInput schema / properties / fallback / description
      Previous value: -"fallback= modifier for @read"New value: +"Value to use when the file or key is not found"
    • changedInput schema / properties / key / description
      Previous value: -"key= modifier for @read"New value: +"If reading a config file, extract this key only"
    • changedInput schema / properties / path / description
      Previous value: -"path= modifier for @read"New value: +"File path to read (relative to workspace root)"
    • changedInput schema / properties / schema / description
      Previous value: -"schema= modifier for @read"New value: +"JSON Schema to validate file contents against"
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true. Description adds useful context about embedding file contents into rendered context and extracting specific keys from structured files, which goes beyond the annotation.

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 clear sentences with no waste. Purpose, usage, and sibling differentiation are front-loaded.

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 4 parameters and output schema exists, the description covers purpose, usage, and behavioral traits adequately. No need to mention return values due to output schema.

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?

Schema coverage is 100%, so baseline is 3. The description mentions 'extract specific keys' which relates to the key parameter, but adds minimal extra meaning beyond the schema descriptions.

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 states 'Read and embed file contents' with a specific verb and resource. It distinguishes from sibling tools like perseus_list and perseus_tree by noting they are for browsing before reading.

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?

Explicitly says 'use to inject config values, environment files, or any text file' and advises using perseus_list/perseus_tree to browse before reading, providing clear when-to-use and alternatives.

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/Perseus-Computing-LLC/perseus'

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