Skip to main content
Glama

Corpus figures and filter values

banjul_facets

Lists available filter values and counts to narrow searches across African Commission and Court human rights decisions by body, decision type, respondent State, cited article, judge, and year.

Instructions

Corpus: decisions of the African Commission on Human and Peoples' Rights (from its library) and English judgments, rulings, orders and separate opinions of the African Court on Human and Peoples' Rights (from AJUDATA), split into their numbered paragraphs. Scanned decisions were read by OCR: check the PDF before quoting. Corpus size and the values the filters of banjul_search accept: bodies, kinds of decision, respondent States, articles with findings (with counts), the most cited decisions, judges who wrote separate opinions, years.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "banjul_facets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, and it does add real context: corpus provenance (Commission library, AJUDATA), paragraph-level splitting, and an OCR caveat warning that scanned decisions should be verified against the PDF before quoting. It does not state the read-only nature explicitly, nor the shape or size of the returned figures, leaving some behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, with the OCR verification warning placed prominently before the facet enumeration. The trailing list is long but each entry names a distinct facet dimension, so it earns its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must convey what comes back; it does so by enumerating the facet dimensions and noting counts for articles with findings. What is missing is the response format (labels vs. identifiers, whether counts are returned for every facet), which an agent would need to consume the result reliably.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to document and the schema imposes nothing. The description instead characterizes the facet categories returned, which is useful but is output description rather than parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the resource concretely: corpus size figures plus the enumerated filter values (bodies, decision kinds, respondent States, articles with findings, most-cited decisions, separate-opinion judges, years). It is clearly a metadata/facet endpoint rather than a search or fetch, which separates it from banjul_search and banjul_get_decision, though the opening sentence is corpus description rather than a crisp verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The tie to banjul_search is implied by 'the values the filters of banjul_search accept', which hints this should be consulted to discover valid filter values. There is no explicit when-to-use statement, no statement of what it does not do, and no instruction on ordering relative to banjul_search.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.