ground-in-docs

Ground concept answers in the repo's own docs

This repo ships three curated reference docs specifically so an agent's explanations of Cardano concepts stay accurate and consistent with how the cardano-mcp server itself models these ideas, rather than drifting toward generic, possibly-outdated blockchain explanations from general training data:

• src/resources/eutxo-context.md — the eUTxO model: UTxOs, validators, datums vs redeemers, how balances work without accounts.
• src/resources/governance-context.md — CIP-1694 / Conway-era governance: DReps, the constitutional committee, SPOs, the seven governance action types, treasury withdrawals, voting.
• src/resources/aiken-stdlib.md — Aiken standard library reference used by the contracts module's tools (get_aiken_stdlib_docs, scaffold_validator, explain_eutxo_model).

Workflow

1. Before answering a question about eUTxO mechanics, Aiken/validator concepts, or CIP-1694 governance, read the relevant file(s) above with the Read tool.
2. Base the answer on what those docs actually say. If the docs and your general knowledge would suggest different framing or terminology, prefer the docs — they're what this project's own tools (explain_eutxo_model, the governance module, get_aiken_stdlib_docs) are aligned with, so answers should stay consistent with what the server itself would tell a caller.
3. If the question goes beyond what these docs cover (e.g. a very specific protocol parameter, a recent CIP not yet reflected here, an Aiken language feature outside the stdlib doc), say so explicitly rather than quietly filling the gap from general knowledge — the point is to be honest about the boundary between "grounded in this project's docs" and "my general understanding."
4. When these docs would benefit from an update (they're missing something a user needed), say so — don't silently patch the answer without flagging that the source doc could be extended.