ai.qompass/periscope

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on.

4 of 16 tools are described as changing something (creating, editing, deleting, sending or running).

• attention_alignmentreads or searches

  “Alignment between your published focus and a partner agent's focus, measured only inside one saliency snapshot frame (Jaccard overlap, shared targets, shared top).”

  1 input, 1 required

  • agent_idstringrequired“The partner agent whose advertised focus to read or compare against.”
• attention_decidedoes something elsedescribed as changing data

  “Coordination decision against a partner agent's focus: parallel (no contention), serialize (same top target — the named holder proceeds, you defer), or reject (stale frame or invalid focus — re-snaps…”

  1 input, 1 required

  • agent_idstringrequired“The partner agent whose advertised focus to read or compare against.”
• attention_focusreads or searches

  “Read a partner agent's currently advertised focus (ordered salient targets + the saliency snapshot hash it was computed from) from the coordination board.”

  1 input, 1 required

  • agent_idstringrequired“The partner agent whose advertised focus to read or compare against.”
• attention_publishcreates or changes datadescribed as changing data

  “Publish your attention focus to the coordination board.”

  1 input, 1 required

  • focusobjectrequired“A focus document: {agent_id, snapshot_hash, seq, targets[]} — ordered salient targets, most salient first.”
• broker_statuson 1 other serverreads or searches

  “Report the broker mode (managed or attached), the editor version, its config root, and its working directory.”

  Takes no inputs.

• get_definitionon 6 other serversreads or searches

  “Definitions of the symbol at a position, from the editor's attached language servers, merged across clients.”

  3 inputs, 3 required

  • characterintegerrequired“0-based character offset in UTF-16 code units (the LSP convention).”
  • lineintegerrequired“0-based line number.”
  • pathstringrequired“Absolute path of the file to inspect.”
• get_diagnosticson 6 other serversreads or searches

  “Diagnostics for one file from every source the editor aggregates (language servers and the linter pipeline), each entry naming its producing tool in `source`.”

  1 input, 1 required

  • pathstringrequired“Absolute path of the file to inspect.”
• get_document_symbolson 1 other serverreads or searches

  “The symbol outline of one file, flattened with container names, from the editor's attached language servers.”

  1 input, 1 required

  • pathstringrequired“Absolute path of the file to inspect.”
• get_hoveron 1 other serverreads or searches

  “Hover text (types, documentation) for the symbol at a position, from the editor's attached language servers.”

  3 inputs, 3 required

  • characterintegerrequired“0-based character offset in UTF-16 code units (the LSP convention).”
  • lineintegerrequired“0-based line number.”
  • pathstringrequired“Absolute path of the file to inspect.”
• get_referenceson 4 other serversreads or searches

  “References to the symbol at a position, merged across the editor's attached language servers.”

  4 inputs, 3 required

  • characterintegerrequired“0-based character offset in UTF-16 code units (the LSP convention).”
  • include_declarationboolean
  • lineintegerrequired“0-based line number.”
  • pathstringrequired“Absolute path of the file to inspect.”
• list_dapreads or searches

  “The debug setup the config ships: per-language dap modules, adapters registered with nvim-dap right now, and launch configurations by filetype.”

  Takes no inputs.

• list_formattersreads or searches

  “Every formatter in the editor config's registry.”

  Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.