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

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

Name	Required	Description
`url`	Yes
`path`	Yes
`title`	No
`content`	No
`documents`	No
`next_steps`	Yes	Suggested next actions, present in every response, errors included. A step with a "tool" field can be taken with that tool.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedNov 4, 2026

changedOutput schema / properties / next_steps / description

Previous value: -"What to do next. A step with a \"tool\" field can be taken with that tool."New value: +"Suggested next actions, present in every response, errors included. A step with a \"tool\" field can be taken with that tool."

addedOutput schema / properties / next_steps / items / description

Added value: +"A natural follow-up the agent might take. `tool` names the MCP tool for the same step. A step may group several `steps`."

addedOutput schema / properties / next_steps / items / properties / action

Added value: +{
+  "description": "A short name for the step.",
+  "type": "string"
+}

addedOutput schema / properties / next_steps / items / properties / body

Added value: +{
+  "additionalProperties": {},
+  "description": "A request body to send, for POST steps.",
+  "properties": {},
+  "type": "object"
+}

addedOutput schema / properties / next_steps / items / properties / description / description
```
Added value: +"What the step is and why an agent might take it."
```

addedOutput schema / properties / next_steps / items / properties / hint

Added value: +{
+  "description": "How to fill in the step, where it needs filling in.",
+  "type": "string"
+}

addedOutput schema / properties / next_steps / items / properties / method

Added value: +{
+  "description": "HTTP method for url.",
+  "type": "string"
+}

addedOutput schema / properties / next_steps / items / properties / note

Added value: +{
+  "description": "Something to know before taking the step.",
+  "type": "string"
+}

addedOutput schema / properties / next_steps / items / properties / steps

Added value: +{
+  "description": "Steps grouped under this one, each the same shape, a description where it needs one.",
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "action": {
+        "description": "A short name for the step.",
+        "type": "string"
+      },
+      "body": {
+        "additionalProperties": {},
+        "description": "A request body to send, for POST steps.",
+        "properties": {},
+        "type": "object"
+      },
+      "description": {
+        "description": "What the step is and why an agent might take it.",
+        "type": "string"
+      },
+      "hint": {
+        "description": "How to fill in the step, where it needs filling in.",
+        "type": "string"
+      },
+      "method": {
+        "description": "HTTP method for url.",
+        "type": "string"
+      },
+      "note": {
+        "description": "Something to know before taking the step.",
+        "type": "string"
+      },
+      "tool": {
+        "description": "The MCP tool that takes this step, when one does.",
+        "type": "string"
+      },
+      "url": {
+        "description": "Where to go.",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / next_steps / items / properties / tool

Added value: +{
+  "description": "The MCP tool that takes this step, when one does.",
+  "type": "string"
+}

addedOutput schema / properties / next_steps / items / properties / url

Added value: +{
+  "description": "Where to go.",
+  "type": "string"
+}

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

C2.8/5.0

Behavior3/5

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

Annotations already declare read-only, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that content is returned as markdown and mirrors the public docs site, but says nothing about missing-path errors or how category listing output differs from a page body.

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

Conciseness3/5

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

It is short, but it is a sentence fragment with a parenthetical that jumps between two ideas (example path and category listing) rather than leading with the action. No wasted padding, but the structure is loose.

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

Completeness3/5

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

With one parameter, full schema coverage, an output schema, and read-only annotations, the description only needs to add orientation. It does supply the markdown format and site equivalence, but leaves the category-listing behavior ambiguous enough to matter for invocation.

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 schema already documents the path parameter with an example. The description adds a second example (a category path that lists contents) and the 300-char context is left to the schema, so it matches but does not exceed the schema baseline.

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

Purpose3/5

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

The description names the resource (documents in the sanctuary's writing) and implies retrieval as markdown by a 'path', but it never states a verb such as 'read' or 'return'. It does not distinguish itself from read_song or browse/search, which an agent could easily confuse for document access.

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

Usage Guidelines2/5

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

There is a passing hint that a category path like 'practice' will list a category, which is useful, but no explicit statement of when to use this versus browse or search. The site reference (achurch.ai/docs) is context, not routing guidance.

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.