Where everything is written down.

Every part of agoramcp is documented on the page that owns it: connecting on the quickstart, the servers on the MCP page, the HTTP contract on the API page, the tools themselves in the catalogue. Nothing is explained twice.

What is left over is this page: the words those pages use without stopping to define them, the rules that hold across all of them, and a straight answer to which one you want.

Start here

Connect a clientOne command, or one entry in a config file you already have.See what there is to askEvery country, source and tool, with arguments and an example each.Call one without an agentThe same tools over plain HTTP, for a script or a notebook.

The words this site uses.

A handful of nouns carry most of the documentation. Each one is defined here once, and used everywhere else without ceremony.

Source: One official registry, adapted: its own tools, its own publisher, its own licence. A source is the smallest thing you can point a client at.; The catalogue
Country server: Every source a country mounts, behind one address. Reach for it before you know which registry holds the answer; reach for a single source when you already do.; MCP
Tool: One question a source can answer, with typed arguments and a description written for a model to read. A tool is what a client calls and what an HTTP request addresses.; The catalogue
Prefix: What a country server puts in front of a tool name so two registries can both have a search_organizations, as in diavgeia_search_organizations. On a source's own server the tools keep their plain names.; MCP
Envelope: What an HTTP response wraps around data, the tool's own result: which source and tool answered, and the provenance that has to travel with the data.; API
Attribution: The line the publisher asks you to show wherever you show their data. It is a condition of the licence, not a courtesy, and it arrives with every answer.; Licences
ADA: The code every act published under the Greek Transparency Programme carries, unique to that act. Given one, you can fetch the record, its signed PDF and its history.; Diavgeia
ADAM: The procurement equivalent: the code that identifies one document in the public contracts registry (a request, a notice, a contract or a payment order).; KIMDIS

Rules that hold everywhere.

True of every source, every tool and every address, so no other page has to say them again.

Country, then source, then tool
Every address is built the same way and in that order: /gr/mcp is a country, /gr/mcp/diavgeia is one of its sources, /gr/api/diavgeia/search_decisions is one of that source's tools. Countries are ISO 3166-1 alpha-2, lowercased.
Tool names are a verb and a noun
search_ takes a question and returns matches, get_ takes an identifier and returns one record, list_ returns a fixed set with no question to ask. A name tells you which of the three you are about to do before you read its arguments.
Dates are YYYY-MM-DD
In every date argument and every date in a record, no exceptions and no locale. Ranges are two arguments rather than one string.
Greek is transliterated here, never in the data
Names are written in Latin script on this site because a reader without Greek should still be able to say them. The records themselves are untouched: a subject, a body's name or an attribution line comes back exactly as the registry wrote it.

Which page answers what.

One job each. If two pages would both answer your question, the one listed here is the one that does it properly.

QuickstartHow do I get my client talking to it?The command or config entry per client, and nothing about what happens afterwards.MCPWhat are these servers, and what happens on a call?The addresses and the request lifecycle, not the snippets, which are the quickstart's.APIHow do I call a tool without an agent?The HTTP contract end to end: addresses, arguments, the envelope, the error codes and the limits.LiveWhat does a real answer actually look like?One call at a time, with arguments you edit: the response, not the contract around it.All sourcesWhat can I ask, and of which registry?Every country, source and tool, each with its arguments and the example it ships with.Use casesWhat does a whole question look like?Four worked examples and the path of tools each takes. Illustrations, not reference.ChangelogWhat changed, and when?Every commit in the repository, newest first, each with the version it landed at.StatusIs it answering right now?A live check per registry, and how long each one took.LicencesWhat may I do with the data?What each licence asks of you, and the exact line to credit each publisher with.