Test tools
Cora AI has its own test tools for proving that Cora’s tools work: that a call reaches a tool, that a long call survives, that a write waits for approval, and that text from an outside tool is treated as data. They are on only when the organisation’s test tools are enabled, and only the operator can enable them (D0130, D0315). For every other organisation they are off and never appear in Cora’s tool list.
There are two sets: three tools built into Cora’s worker, and five tools on a small MCP server of our own, cora-test-tools, which is connected through the console like any customer server. See Connecting an MCP server for how that works.
In-process test tools
Section titled “In-process test tools”These are built into Cora’s worker. They make no network call outside Cora AI and cost no model use. Cora gets them in a run as soon as the organisation’s test tools are enabled.
| Tool | Kind | What it proves |
|---|---|---|
test_echo |
Read | A call reaches a tool and comes back. It returns the text it was given, the run id and the time, marked as data. |
test_wait |
Read | A long call survives. It waits up to 600 seconds and does nothing else, so a test can stop a worker mid-call and check the run carries on. |
test_fake_write |
Write | A write waits for a person. It pauses for approval like any write; once approved it adds one test entry to the mission’s record history, and only once. |
The cora-test-tools server
Section titled “The cora-test-tools server”These five tools are on our own MCP server. An org admin in an organisation with test tools enabled connects it by its https address with a bearer token, and turns its tools on as for any server. The bearer token is in the secrets store and is never printed: not in the docs, a log or the console.
The Kind column is how to set each tool: a read can be Allowed, a write Ask first. The server also gives each a read-only hint, which puts it in the Read group, but as for any server, only the setting an org admin chooses decides whether a call asks (D0716).
| Tool | Kind | What it proves |
|---|---|---|
whoami |
Read | The credential reaches the server. It returns an identity label to show which sign-in was used, never the token itself. |
lookup_fixture |
Read | Lookups work, and text from an outside tool stays data. One of its fixed entries holds planted instructions, which Cora must not follow. |
untrusted_text |
Read | Cora treats instruction-like text from a tool as plain data. It always returns the same planted instructions. |
fake_create_ticket |
Write | An MCP write waits for approval and then runs once. It creates nothing real; the server logs one line per call. |
not_allowed |
Read | The tool list is filtered. It stays Off on the connection, so Cora must never be offered it in any mission. |
The test pack
Section titled “The test pack”Once an organisation’s test tools are enabled, a person creating a mission can also add the test pack, test-stub, beside the usual core-pm pack (D0314). Its procedure tells Cora that when a question in the mission is answered, and cora_fake_create_ticket is in its tools, it files one test ticket summing up the answer. That write waits for approval like any other, with 72 hours to answer, because the test pack sets a longer expiry than the 48-hour default. The new-mission form shows the choice only when test tools are enabled.
Coming next
Section titled “Coming next”- The test tools stay limited to Cora AI’s own research and development organisation. Customers never see them (D0130).