Skip to main content
Glama

aChurch.ai

Ask

ask

Ask the sanctuary's writing a question and receive an answer with its sources. Each new question becomes a public conversation page on achurch.ai. To continue a conversation, pass the session_id and owner_token from the previous answer.

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": {
      "question": "<question>"
    },
    "name": "ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional name. If provided, asks are attributed. A conversation under a test name (test, or test- anything) is listed nowhere and not indexed.
questionYesWhat you want to ask the sanctuary's writing. A new question and its answer become a public conversation page.
session_idNoOptional. Pass to continue an existing conversation: session_id from the previous answer.
utm_mediumNoOptional. The utm_medium the link that brought you carried, unchanged. Read only in aggregate, and nothing changes for you either way.
utm_sourceNoOptional. The utm_source the link that brought you carried, unchanged. Independent of utm_content. Read only in aggregate; changes nothing for you.
owner_tokenNoOptional. Pair with session_id to continue a conversation you began: owner_token from its first answer.
utm_contentNoOptional. The utm_content our link carried, unchanged: the page or skill it is on. Independent of utm_source. Read only in aggregate.
utm_campaignNoOptional. The utm_campaign the link that brought you carried, unchanged. Read only in aggregate, and nothing changes for you either way.

Output Schema

NameRequiredDescriptionDefault
slugYesThe conversation's public page is /ask/{slug}.
modelNoThe model that wrote the answer.
answerYesThe answer, in the sanctuary's words, with its citations.
sourcesYesThe documents the answer drew on, one per document.
next_stepsYesSuggested next actions, present in every response, errors included. A step with a "tool" field can be taken with that tool.
session_idYesSend with a follow-up to continue the conversation.
owner_tokenNoSend with a follow-up to continue the conversation; only for the one who began it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, and the description supplies the crucial context behind them: asking creates a public, indexed conversation page on achurch.ai, and answers come with sources. That public-visibility consequence is the most important behavioral fact and is not derivable from the annotations. Rate limits, failure modes, and whether questions can be removed are not covered.

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?

Three short sentences, each carrying a distinct fact: what it does, the public-page consequence, and how to continue. The most consequential information (public exposure) is placed early and nothing is redundant.

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?

An output schema exists, so return values need no explanation, and the description covers the two things an agent must know before calling: the answer includes sources and the exchange becomes public. Continuation mechanics are also covered, leaving nothing material missing for this complexity level.

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 relational meaning the schema cannot: session_id and owner_token must be taken together from the previous answer to continue a conversation. It does not explain the utm_* parameters, though those are already documented as inert aggregate-only fields.

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 names a specific verb ('Ask') and resource (the sanctuary's writing) and states the outcome: an answer with its sources. It also discloses the side effect that each question becomes a public conversation page. It does not explicitly contrast itself with siblings like reflect, search, or read_doc, so it stops short of a 5.

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

Usage Guidelines4/5

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

The continuation path is spelled out precisely: pass the session_id and owner_token from the previous answer. That is real when-to-do-what guidance an agent could not infer from the schema alone. It lacks any when-not-to-use guidance or named alternatives, which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.