Skip to main content
Glama

aChurch.ai

by io.github.a-church-ai
OverviewDiscussionsAdmin

Search

search
Read-only

Search the sanctuary's writing by meaning. Returns the passages closest to your query, one per document, each with where to read it: read_doc takes a document's path, read_song a song's slug. Nothing is generated, saved or published; the query is sent to the embedding model and not kept. Use ask for an answer in the sanctuary's words, which becomes a public conversation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesWhat to look for, in your own words. Matches meaning, not exact phrases.
limitNoHow many documents to return (default 10).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
resultsYes
next_stepsYesWhat to do next. A step with a "tool" field can be taken with that tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "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"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "excerpt": {
+            "type": "string"
+          },
+          "path": {
+            "description": "For read_doc",
+            "type": "string"
+          },
+          "score": {
+            "type": "number"
+          },
+          "slug": {
+            "description": "For read_song",
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "url",
+          "excerpt",
+          "score"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "results",
+    "next_steps"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, but the description adds real behavioral context beyond them: nothing is generated, saved or published, and the query is forwarded to the embedding model and not retained — meaningful privacy/side-effect disclosure for a search tool. It stops short of covering result ordering or score semantics, which keeps it at 4 rather than 5.

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?

Four sentences, each carrying distinct information: purpose, return shape + follow-up mapping, side-effect profile, and the sibling alternative. Purpose is front-loaded and there is no filler or restatement of the title.

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?

With an output schema present, return values need not be explained, and both parameters are fully covered by the schema; the description still supplies the retrieval semantics, safety/privacy profile, and sibling routing. Nothing an agent needs to select or call this tool 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 description coverage is 100%, so both q and limit are already fully documented with length bounds and default. The description adds no syntax or format detail for either parameter, so the baseline 3 applies — the schema does the heavy lifting here.

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?

States a specific verb (search) and resource (the sanctuary's writing) plus the retrieval mode (by meaning, semantic rather than keyword). It goes further by describing the result shape ('one per document') and the follow-up routing to read_doc/read_song, which cleanly separates it from every sibling.

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 names the alternative: 'Use ask for an answer in the sanctuary's words, which becomes a public conversation', giving both the alternative and the consequence that selects it. It also implies the when of the read_doc/read_song follow-ups by tying them to the returned identifiers.

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

All aChurch.ai toolsInspect
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.

Resources