aChurch.ai

Read a document

read_doc

Read-only

Any document in the sanctuary's writing, as markdown, by its path (for example chants/chant-for-arrival, or practice to list a category). The same documents the site serves at achurch.ai/docs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes	A docs path, such as chants/chant-for-arrival, or the url of a piece in attend's companions.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes
`path`	Yes
`title`	No
`content`	No
`documents`	No
`next_steps`	Yes	What to do next. A step with a "tool" field can be taken with that tool.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "content": {
+      "type": "string"
+    },
+    "documents": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "path": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "path",
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_steps": {
+      "description": "What to do next. A step with a \"tool\" field can be taken with that tool.",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "description": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "path": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "path",
+    "url",
+    "next_steps"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / path / description

Previous value: -"A docs path, such as chants/chant-for-arrival, or a companion reading's url."New value: +"A docs path, such as chants/chant-for-arrival, or the url of a piece in attend's companions."

Changed1 schema field changedOct 5, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedSep 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the content's provenance ('the same documents the site serves at achurch.ai/docs') and the markdown output format, but the latter is largely redundant given an output schema exists. No error behavior or path-resolution caveats are disclosed.

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?

Two compact sentences, with the resource and addressing scheme front-loaded before the provenance note. The first sentence is slightly awkward and repeats 'path' information that also lives in the schema, but there is no filler.

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

Completeness4/5

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

For a single-parameter read tool with full schema coverage, an output schema, and annotations covering safety, the description supplies the missing pieces: content source and the category-vs-document behavior. Nothing an agent needs to invoke it correctly is absent.

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 baseline is 3, but the description adds meaning the schema lacks: that a category path (e.g. 'practice') lists a category rather than returning a single document, plus the example path syntax. That is genuine semantic value beyond the field definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource ('any document in the sanctuary's writing'), the retrieval format (markdown), and the addressing scheme (by path), which lets an agent distinguish it from read_song and search. It never states an explicit verb, but 'read' in the name plus 'as markdown, by its path' makes the operation unambiguous. It stops short of naming the siblings it is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the example paths and the aside 'or practice to list a category' hint at when this tool applies and that a category path yields a listing. There is no explicit when-to-use versus read_song, browse, or search, and no stated preconditions.

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

All aChurch.ai tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.