Djinious
Data governance · in-app assistant and MCPGeospatial & territory

Agent-assisted catalogue review

Put the question to an agent that can read every profile, and get an answer with the tool calls that produced it.

DjiniousMap
The API tokens tab of DjiniousMap settings, listing three minted MCP tokens — a laptop client, a scheduled audit and a read-only notebook — each with its creation date, last-used state and its own Revoke control.

Reviewing a catalogue is exactly the kind of tedious, mechanical reading a person does badly and an agent does well: open each profile, check whether a CRS was inferred, note the findings.

The assistant works the same API under the same tenancy model, proposes before it acts, and shows every call it made. An external agent gets the same reach through MCP, and its transcript can be mirrored back into the app so the team sees the work.

How it runs

  1. Ask

    Ask the assistant which datasets cannot be placed on a map.

    Assistant
  2. Watch the trace

    Watch the tool calls resolve, including the ones that return nothing.

    Plan-first
  3. Read the cards

    Get the answer with the catalogue’s own cards inline, not a paraphrase.

    MCP
  4. Mirror

    Mirror an external agent’s session in if the work happened elsewhere.

    Conversation mirroring

An agent auditing the catalogue, mirrored live

DjiniousMap
An external agent is asked which datasets the platform will refuse to draw. It searches the catalogue, reads two profiles, and explains the difference between a dataset with no inferable CRS and one whose publisher simply declared the wrong code. Recorded against the seeded development stack; the agent’s turns are scripted so the recording is reproducible.