fss_policy_kg_get_corpus_overview – 1 MCP server offers this tool
What it usually takes
category– in 1 of 1layer– in 1 of 1limit– in 1 of 1offset– in 1 of 1
No server marks it as only reading: treat it as able to change data.
From each publisher's own tool list. We never call a tool.
Servers
| Server | Inputs | Read-only? |
|---|---|---|
fss-policy-kg co.huggingface.brockwebb/fss-policy-kg The corpus landscape in ONE call — CALL THIS FIRST for any coverage / gap / 'what documents are there' / 'are there gaps in X' question. Returns the document inventory (each with layer, category, issuing agency, obligation_count, and mention-coverage stats), the corpus totals, the served export version, and the layer model — so you can see where obligations concentrate and how well each document is concept-tagged before drilling in. Read the coverage correctly: resolved_mention_edges / concept_reachable_share measure CONCEPT TAGGING, which is sparse by design — a low share means under-tagging, NOT that the document lacks the topic. raw_mention_count vs resolved_mention_edges shows the untagged remainder. Use search_text for authoritative topic presence. Returns: A JSON envelope; results are documents sorted by obligation_count (largest first), each with, doc_id, title (snippet), agency, layer, category, is_stale, obligation_count,, raw_mention_count, resolved_mention_edges, concept_rea | category,layer,limit,offset | Not stated |