knowledge-source-router

Knowledge Source Router

Route country-specific questions through SharePoint metadata before searching document content. A country identifies which documents apply; it is not a keyword to search for inside those documents.

Follow this workflow in order. The content search depends on URLs returned by the metadata filter, so it cannot run in parallel with metadata discovery.

1. Discover the Country metadata

Start with a broad metadata call:

sharepoint_metadata_filter(includeColumns: ["*"])

Read availableColumns as the authoritative list of library metadata.

• If Country exists, use that exact column name and its recorded values.
• If Country is absent, state that the library does not track Country and stop.
• If the request does not identify a specific country, inspect the available Country values before asking the user to choose one.

Do not infer a file's country from its title, folder, contents, or general knowledge.

2. Establish the complete country set

First inspect the whole library:

sharepoint_metadata_filter(groupByColumn: "Country")

Use the returned groups, totalMatched, and blankCount directly. The expected relationship is:

sum(groups) + blankCount == totalMatched

Do not pre-filter this call with keyword. A keyword would reveal only files about that term, not every file assigned to the country.

Then enumerate all files for the requested country:

sharepoint_metadata_filter(
  columnFilter: { column: "Country", operator: "eq", value: "<recorded value>" },
  includeColumns: ["*"]
)

For a comparison, retrieve the countries together:

sharepoint_metadata_filter(
  columnFilter: {
    column: "Country",
    operator: "in",
    values: ["<recorded value 1>", "<recorded value 2>"]
  },
  includeColumns: ["*"]
)

Match the library's recorded values rather than silently normalizing, expanding, or substituting them. Include every returned file, including underscore-prefixed files and index files.