cedulon
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cedulon_spendA | Policy-gated spend on the mock rail. Allow returns a signed COSE receipt JSON. Deny returns the fail-closed reason. |
| cedulon_auditA | Reconcile the in-process receipt chain and checkpoint against the rail extract: this server's own ledger, or a signed extract you present. Returns audit: balanced or findings, names the account, rail and window it was computed over (scope) when an extract declared one, and counts the class every receipt and row landed in (counts). |
| cedulon_verify_receiptA | Verify a spend receipt COSE_Sign1 (and payee countersignature when present). Supply expectIssuerKeyPem to check it against a key you already hold; without one the receipt is only checked against the key it carries, which any key satisfies. |
| cedulon_export_ledgerA | Export receipts, checkpoint, and rail extract in the same JSON shape as npm run demo:export, with the findings, guarantee and counts of the audit over this server's own ledger. |
| cedulon_statusA | Server version, policy summary, receipt count, and chain head hash. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool maps to a distinct operation: status for server health and context, spend for initiating a payment, audit for reconciliation, verify_receipt for signature validation, and export_ledger for extracting data. There is no meaningful functional overlap between any pair.
All names use lowercase snake_case and share the cedulon_ prefix, which is a solid convention. However, the action pattern is slightly inconsistent: status and audit are noun-style, while spend, verify_receipt, and export_ledger are verb or verb_noun style.
Five tools is well-scoped for a focused payment/audit server. Each tool has a clear role—information, spend, verification, audit, export—and none feels redundant or excessive.
The tool set covers the core workflow: spend creates a receipt, verify_receipt validates it, audit reconciles the ledger or a presented extract, and export_ledger provides data portability. Status supplies the necessary server-level context, so there are no obvious dead ends for the stated domain.