NinFenz Content Gate

Overview Schema Source Related Servers Discussions Admin

Read library entry

library_read

Read-onlyIdempotent

Fetch a single library catalog entry by ID to return its frontmatter record and full body; use it after search resolves the ID, not for searching or reading modules, pipelines, or assets.

Instructions

Read one library catalog entry by ID, returning its frontmatter record and body. Use it after library_search resolves the ID; do not use it to search (library_search) or to read modules, pipelines, or assets (module_read / pipeline_read / asset_read). The ID is the canonical stem without the .md suffix and matching is case-insensitive (for example NF-1); an unknown ID returns an error carrying the requested value and repair guidance. Reads one local file and returns its full text without truncation. Local-only; no auth or rate limits.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`entry_id`	Yes	Catalog ID, case-insensitive (for example NF-1 or nf-worldcampus-monyeah777-1).

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Canonical catalog ID.
`path`	Yes	Repository-relative Markdown path.
`text`	Yes	Full Markdown body as stored on disk.
`bytes`	Yes	UTF-8 byte length of text.
`found`	Yes	True when the entry was located.
`status`	Yes	Catalog lifecycle status (for example active).
`frontmatter`	Yes	Parsed YAML frontmatter as JSON; keys vary by entry.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Oct 18, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds valuable behavioral details beyond those annotations: unknown IDs return an error with the requested value and repair guidance, reads are local-only, the full text is returned without truncation, and there are no auth requirements or rate limits. This is rich transparency 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 front-loaded with the core purpose, then immediately covers routing, ID format, error behavior, read characteristics, and environment constraints. Every sentence carries useful information, with no redundant or filler content.

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's simplicity, the 100% schema description coverage, and the presence of an output schema, the description is fully complete. It covers purpose, sibling differentiation, ID format, error handling, return behavior, and local-only constraints, leaving no critical gap for an agent.

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

Parameters4/5

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

Schema coverage is 100%, so the single parameter's case-insensitivity and example are already documented. The description adds additional format semantics not present in the schema: the ID is 'the canonical stem without the .md suffix' and matching is case-insensitive. This meaningfully extends parameter understanding beyond the structured field.

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 a specific verb and resource: 'Read one library catalog entry by ID, returning its frontmatter record and body.' It also explicitly distinguishes this tool from siblings, naming library_search, module_read, pipeline_read, and asset_read as alternatives. An agent can select this tool without opening another schema.

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?

Usage is explicit: 'Use it after library_search resolves the ID; do not use it to search ... or to read modules, pipelines, or assets.' This provides both when-to-use and when-not-to-use guidance, along with named alternatives. Nothing is left to inference.

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

Deploy Server