trip2g

Walk a note's table of contents level by level (progressive disclosure). Canonical call: expand(path=<result.note_path>, toc_path=[...]) — copy path verbatim from a search result's note_path field. Returns the direct children of a TOC node: omit toc_path (or pass []) for the top-level sections, or pass a toc_path to list that section's subsections. Each child has title, level, path, and has_children. A section with subsections lists them; a section without subsections is returned in full (what note_html gives for that toc_path, plus section_html in the payload), so no second call is needed to read a leaf. This cannot be turned off, and a client that wants only structure never triggers it: has_children on each listed child says where descending would turn into reading.

{
  "type": "object",
  "properties": {
    "href": {
      "type": "string",
      "description": "String note href, copied verbatim from a search result's href field"
    },
    "note_id": {
      "type": "number",
      "description": "Same as pid: non-negative integer (uint64) note id, copied verbatim from a search result's note_id field. Not a path, slug, or match_id. Prefer path"
    },
    "path": {
      "type": "string",
      "description": "String note path, e.g. \"concepts/maska-i-glubina.md\" — copy verbatim from a search result's note_path field. The default, preferred way to reference a note"
    },
    "pid": {
      "type": "number",
      "description": "Non-negative integer (uint64) note id, copied verbatim from a search result's note_id field. Not a path, slug, or match_id. Prefer path"
    },
    "toc_path": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Breadcrumb path to the node to expand, e.g. [\"Chapter 1\"]. Omit or [] for the top level."
    }
  }
}

Walk a remote note's table of contents level by level inside a connected knowledge base (progressive disclosure), same as expand. Canonical call: federated_expand(kb_id=..., path=<result.note_path>, toc_path=[...]). Omit toc_path for the top level, or pass a toc_path to list that node's subsections. A section with subsections lists them; a section without subsections is returned in full, as federated_note_html would return it — has_children on each listed child says where that happens.

{
  "type": "object",
  "properties": {
    "href": {
      "type": "string",
      "description": "String remote note href, copied verbatim from a federated_search result's href field"
    },
    "kb_id": {
      "type": "string",
      "description": "Target knowledge base id; nested bases use '/' (e.g. \"philosophers/nietzsche\" routes through the 'philosophers' peer, recursively). Federation nests up to 3 levels deep (kb_id path segments); a deeper path is rejected."
    },
    "note_id": {
      "type": "string",
      "description": "Same remote note id as pid, but as a STRING (uint64) — stringify the federated_search result's note_id field. Prefer path"
    },
    "path": {
      "type": "string",
      "description": "String remote note path, copied verbatim from a federated_search result's note_path field"
    },
    "pid": {
      "type": "number",
      "description": "Non-negative integer (uint64) remote note id, copied verbatim from a federated_search result's note_id field. Prefer path"
    },
    "toc_path": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Breadcrumb path to the node to expand. Omit or [] for the top level."
    }
  },
  "required": [
    "kb_id"
  ]
}

Fetch the instructions/guidance for a federated knowledge base by kb_id (e.g. "philosophers/nietzsche") — read a base's own conventions before searching it. Nested bases are addressed with '/' and the call routes through each peer recursively.

{
  "type": "object",
  "properties": {
    "kb_id": {
      "type": "string",
      "description": "Target knowledge base id; nested bases use '/' (e.g. \"philosophers/nietzsche\" routes through the 'philosophers' peer, recursively)"
    }
  },
  "required": [
    "kb_id"
  ]
}

Read a remote note inside a connected knowledge base. Canonical call, copying fields verbatim from a federated_search result: federated_search(kb_id="philosophers/<author>", query) -> federated_note_html(kb_id="philosophers/<author>", path=<result.note_path>) — the standard way to descend into a leaf corpus and read real content there, not hub cards. federated_note_html(kb_id=..., match_id=<match.match_id>) reads just the focused chunk around a hit. Only pass pid/note_id if you already copied that exact id from a result. path is a string like "concepts/x.md"; match_id is "p<pid>:c<chunk>"; a value like ":" or "/hub/goethe.md" is a PATH, not a note_id.

{
  "type": "object",
  "properties": {
    "href": {
      "type": "string",
      "description": "String remote note href or absolute URL, copied verbatim from a federated_search result's href field"
    },
    "kb_id": {
      "type": "string",
      "description": "Target knowledge base id; nested bases use '/' (e.g. \"philosophers/nietzsche\" routes through the 'philosophers' peer, recursively). Federation nests up to 3 levels deep (kb_id path segments); a deeper path is rejected."
    },
    "match_id": {
      "type": "string",
      "description": "String chunk id of the form \"p<pid>:c<chunk>\", copied verbatim from a remote search match's match_id field; alone it is enough to resolve the note"
    },
    "note_id": {
      "type": "string",
      "description": "Same remote note id as pid, but as a STRING (uint64) — stringify the federated_search result's note_id field. Not a path, slug, or match_id. Prefer path or match_id"
    },
    "path": {
      "type": "string",
      "description": "String remote note path, copied verbatim from a federated_search result's note_path field"
    },
    "pid": {
      "type": "number",
      "description": "Non-negative integer (uint64) remote note id, copied verbatim from a federated_search result's note_id field. Not a path, slug, or match_id. Prefer path or match_id"
    },
    "toc_path": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Breadcrumb path to a specific section, e.g. [\"Chapter 1\", \"Introduction\"]. Use toc_path from a federated_search match, or a child path from federated_expand. Wins over match_id when both are given. Without either the whole note comes back."
    }
  },
  "required": [
    "kb_id"
  ]
}

Search connected knowledge bases. Returns snippets with heading breadcrumbs (title > section > subsection) and a precise toc_path per match, same as search; results also carry an absolute kb_id (string) to use verbatim on follow-up calls. Pass kb_id for one base, kb_ids for selected bases, or omit both to fan out. Nested bases are addressed with '/': kb_id "philosophers/nietzsche" routes through the 'philosophers' peer to the base it federates (recursive), up to 3 levels deep. Canonical call: federated_search(kb_id="philosophers/<author>", query) -> federated_note_html(kb_id="philosophers/<author>", path=<result.note_path>) — the standard way to descend into a leaf corpus and read real content, not hub cards.

{
  "type": "object",
  "properties": {
    "detail_limit": {
      "type": "number",
      "description": "How many results include full snippet matches; results beyond this are returned as lightweight previews (title, path, score) to save context (default 3)"
    },
    "kb_id": {
      "type": "string",
      "description": "Target knowledge base id; nested bases use '/' (e.g. \"philosophers/nietzsche\" routes through the 'philosophers' peer, recursively). Federation nests up to 3 levels deep (kb_id path segments); a deeper path is rejected."
    },
    "kb_ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Target knowledge base ids; each accepts the same nested 'peer/base' form as kb_id"
    },
    "limit": {
      "type": "number",
      "description": "Max number of results to return (default 6)"
    },
    "query": {
      "type": "string",
      "description": "Search query"
    }
  },
  "required": [
    "query"
  ]
}

Find remote notes similar to a known note reference inside a connected knowledge base. Preferred: path (a federated_search result's note_path field).

{
  "type": "object",
  "properties": {
    "href": {
      "type": "string",
      "description": "String remote note href, copied verbatim from a federated_search result's href field"
    },
    "kb_id": {
      "type": "string",
      "description": "Target knowledge base id; nested bases use '/' (e.g. \"philosophers/nietzsche\" routes through the 'philosophers' peer, recursively). Federation nests up to 3 levels deep (kb_id path segments); a deeper path is rejected."
    },
    "limit": {
      "type": "number",
      "description": "Max number of results"
    },
    "note_id": {
      "type": "string",
      "description": "Same remote note id as pid, but as a STRING (uint64) — stringify the federated_search result's note_id field. Prefer path"
    },
    "path": {
      "type": "string",
      "description": "String remote note path, copied verbatim from a federated_search result's note_path field"
    },
    "pid": {
      "type": "number",
      "description": "Non-negative integer (uint64) remote note id, copied verbatim from a federated_search result's note_id field. Prefer path"
    }
  },
  "required": [
    "kb_id"
  ]
}

Full tool reference for the trip2g documentation base

{
  "type": "object"
}

Read a note. Canonical calls, copying fields verbatim from a search result: search(query) -> note_html(path=<result.note_path>) reads the whole note; search(query) -> note_html(match_id=<match.match_id>) reads just the focused chunk around a hit (cheaper, targeted); expand(path=<result.note_path>, toc_path=[...]) -> note_html(path=<result.note_path>, toc_path=[...]) reads one exact section. Only pass pid/note_id if you already copied that exact integer from a result's note_id field — never invent one. path is a string like "concepts/x.md"; match_id is "p<pid>:c<chunk>"; a value like ":" or "/hub/goethe.md" is a PATH, not a note_id.

{
  "type": "object",
  "properties": {
    "context_words": {
      "type": "number",
      "description": "Optional future hint for expanding focused reads"
    },
    "href": {
      "type": "string",
      "description": "String note href or absolute URL, copied verbatim from a search result's href field"
    },
    "match_id": {
      "type": "string",
      "description": "String chunk id of the form \"p<pid>:c<chunk>\" (e.g. \"p32:c4\"), copied verbatim from a search match's match_id field. Alone it is enough to resolve the note and reads a focused window around that hit"
    },
    "note_id": {
      "type": "number",
      "description": "Same as pid: non-negative integer (uint64) note id, copied verbatim from a search result's note_id field. Not a path, slug, or match_id. Prefer path or match_id"
    },
    "path": {
      "type": "string",
      "description": "String note path, e.g. \"concepts/maska-i-glubina.md\" — copy verbatim from a search result's note_path field. The default, preferred way to open a note"
    },
    "pid": {
      "type": "number",
      "description": "Non-negative integer (uint64) note id, copied verbatim from a search result's note_id field. Not a path, slug, or match_id — a value like \":\" or \"/hub/goethe.md\" is a path, not a note id. Prefer path or match_id"
    },
    "toc_path": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Breadcrumb path to a specific section, e.g. [\"Chapter 1\", \"Introduction\"]. Use toc_path from a search match, or a child path from expand. Wins over match_id when both are given: match_id is only used when toc_path is absent."
    }
  }
}

Search notes by query. Returns snippets with a heading breadcrumb (title > section > subsection) that locates the approximate section, plus a precise toc_path per match. Each result carries note_path (string) and note_id (integer); each match carries match_id (string, form "p<pid>:c<chunk>"). Drill-down workflow: 1) search to find the approximate section via the breadcrumb; 2) call note_html(path=<result.note_path>, toc_path=[...]) to read the matched section, or expand(path=<result.note_path>, toc_path=[...]) to navigate the note's structure level by level; 3) note_html(path=<result.note_path>, match_id=<match.match_id>) for a focused chunk window. Each match also carries section_url — a link straight to that heading, for citing the section rather than the whole note.

{
  "type": "object",
  "properties": {
    "detail_limit": {
      "type": "number",
      "description": "How many results include full snippet matches; results beyond this are returned as lightweight previews (title, path, score) to save context (default 3)"
    },
    "limit": {
      "type": "number",
      "description": "Max number of results to return (default 6)"
    },
    "query": {
      "type": "string",
      "description": "Search query"
    }
  },
  "required": [
    "query"
  ]
}

Find related notes from a known note reference. Preferred: path (a search result's note_path field). Use this after opening a promising note when you need nearby context.

{
  "type": "object",
  "properties": {
    "href": {
      "type": "string",
      "description": "String note href, copied verbatim from a search result's href field"
    },
    "limit": {
      "type": "number",
      "description": "Max number of results (default 10)"
    },
    "note_id": {
      "type": "number",
      "description": "Same as pid: non-negative integer (uint64) note id, copied verbatim from a search result's note_id field. Not a path, slug, or match_id. Prefer path"
    },
    "path": {
      "type": "string",
      "description": "String note path, e.g. \"concepts/maska-i-glubina.md\" — copy verbatim from a search result's note_path field. The default, preferred way to reference a note"
    },
    "pid": {
      "type": "number",
      "description": "Non-negative integer (uint64) note id, copied verbatim from a search result's note_id field. Not a path, slug, or match_id — a value like \":\" or \"/hub/goethe.md\" is a path, not a note id. Prefer path"
    }
  }
}

Wiki Knowledge Base Instructions

{
  "type": "object"
}