Skip to main content
Glama

Get a decision: metadata, findings and verbatim paragraphs

banjul_get_decision

Retrieve a full African Commission or Court human rights decision by doc_id, including metadata, findings, opinions, citations, and verbatim paragraphs, with paragraph-range or operative-only options.

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. Full record of one decision by doc_id (from banjul_search): metadata, findings, separate opinions or the decision an opinion belongs to, the decisions it cites and that cite it (with paragraphs), and the VERBATIM paragraphs, optionally a range of paragraph numbers or the operative part only. Long decisions are returned in pages of at most 80 paragraphs: use from_para.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "doc_id": "<doc_id>"
    },
    "name": "banjul_get_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYese.g. AfCHPR-D604 or ACHPR-ohebxf4guq-0
to_paraNoLast paragraph number to return.
from_paraNoFirst paragraph number to return.
operative_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses the OCR caveat on scanned decisions, the hard pagination cap of 80 paragraphs, and precisely which sections are returned including the citation network and verbatim paragraph text. It stops short of stating permission/auth requirements or whether the corpus is complete for all years, leaving some behavioral context unstated.

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?

Three dense sentences with the resource and its scope front-loaded, followed by return contents and then pagination instructions in the order an agent needs them. The opening corpus/OCR sentence is long and partly overlaps with what a search tool would describe, but it earns its place by explaining paragraph splitting and the OCR reliability caveat.

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

Completeness5/5

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

There is no output schema, yet the description fully covers what comes back — metadata, findings, opinion relationships, inbound and outbound citations with paragraphs, and verbatim paragraph text — plus the pagination constraint needed to retrieve it all. Nothing an agent needs in order to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 75% and the description meaningfully extends it: doc_id is tied to its source tool with example formats, from_para/to_para are framed as a paragraph range with a pagination rationale, and operative_only is explained as returning just the operative part. It does not clarify whether from_para defaults or how out-of-range values behave, so it is strong but not exhaustive.

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

Purpose5/5

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

The description uses a specific verb and resource ('Full record of one decision by doc_id') and enumerates exactly what the record contains: metadata, findings, separate opinions, citation graph, and verbatim paragraphs. It explicitly distinguishes itself from the sibling banjul_search by noting doc_id comes from that tool, so an agent can tell retrieval apart from search without opening a schema.

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

Usage Guidelines4/5

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

It gives clear operative guidance: obtain doc_id from banjul_search, use from_para for long decisions because responses are capped at 80 paragraphs, and verify against the PDF before quoting OCR'd scans. It lacks an explicit 'do not use this to search — use banjul_search instead' exclusion, which keeps it short of a 5.

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