Skip to main content
Glama

Read a Phygital Brain file

phygital_brain_read_file
Read-onlyIdempotent

Read a Phygital Brain file to return its full text, including forms, templates, language files, skills, or suggested skills/apps; use it when a named file is needed or to see what can be added.

Instructions

Read one of Phygital Brain's own files and return its full text: a form, a template, a language file, a skill, or the suggested skills and apps people can add (start with 'suggested-skills/README.md' and 'suggested-apps/README.md'). Use it when the instructions from phygital_brain_start name a file, or when the person asks what they can add to their brain; if you don't know the exact name, list the folder with phygital_brain_list_files first. A missing file, a folder, or a path outside the skills folder returns an error that says so. It reads only Phygital Brain's files, never the person's brain, and changes nothing.

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

Input Schema

NameRequiredDescriptionDefault
pathYesThe file's path inside Phygital Brain's skills folder, like 'brain-setup/forms/form-1-about-you.html' or 'brain-setup/i18n/ja/templates/root-CLAUDE.md'. Paths that start with a brain folder (About/, Daily/, Projects/...) are in the person's brain, not here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.9
    • changedInput schema / properties / path / description
      Previous value: -"Path inside the skills folder."New value: +"The file's path inside Phygital Brain's skills folder, like 'brain-setup/forms/form-1-about-you.html' or 'brain-setup/i18n/ja/templates/root-CLAUDE.md'. Paths that start with a brain folder (About/, Daily/, Projects/...) are in the person's brain, not here."
  2. First observedv0.1.8

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the added value is the error semantics: a missing file, a folder, or an out-of-scope path returns an error that names the problem. The scope disclosure (never reads the person's brain) is genuinely useful context beyond structured fields; 'changes nothing' merely restates readOnlyHint, which is why this stops short of 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the action and its scope, then tacks on usage, fallback, and error behavior in a compact sequence. Some clauses (the file-type list, the 'changes nothing' tail) are slightly redundant, but nearly every sentence earns its place.

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?

For a single-parameter, side-effect-free read with no output schema, the description covers scope, error behavior, entry-point files, and the sibling fallback. Nothing an agent needs in order to call it correctly is missing.

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% and the path parameter description already gives example paths and the brain-folder exclusion, so the schema carries nearly all parameter meaning. The description adds only the hint that 'suggested-skills/README.md' and 'suggested-apps/README.md' are useful starting paths, which is marginal beyond the schema – baseline 3.

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 gives a specific verb and resource ('Read one of Phygital Brain's own files and return its full text') and enumerates the concrete file kinds, including entry points like 'suggested-skills/README.md'. It also draws a hard boundary against the person's brain, so an agent can distinguish it from phygital_brain_list_files and phygital_brain_start without inspecting the schemas.

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?

It states explicit trigger conditions ('when the instructions from phygital_brain_start name a file' or the person asks what they can add) and an explicit alternative plus fallback ('if you don't know the exact name, list the folder with phygital_brain_list_files first'). That is when/when-not/alternative routing all in one place.

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