Skip to main content
Glama
mining-cadastre-mcp

mining-cadastre-mcp

Détail d'un titre minier

cadastre_get_licence
Read-onlyIdempotent

Retrieve full details of a Burkina Faso mining title by its stable numeric code, including holder, status, dates, location, and OCR anomaly flags. Search by name first to find the exact code.

Instructions

Rend le détail d'un titre minier par son code, l'identifiant numérique que porte la liste publiée. Ce code est stable d'une édition à l'autre : c'est la clé pour suivre un titre dans le temps.

Le code doit correspondre exactement. Pour le trouver, passer par cadastre_search_licences. Si plusieurs enregistrements portent le même code — ce qui signale une anomalie de lecture dans la source — ils sont tous rendus, sans qu'aucun soit choisi à la place de l'appelant.

Le texte vient d'un PDF scanné puis océrisé ; anomalies_de_lecture signale ce qui est douteux, rien n'est corrigé. La donnée reflète la date d'édition et ne fait pas foi : le registre officiel est la seule référence opposable. Ne pas s'en servir pour vérifier un titre sans confirmer auprès de l'autorité citée.

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": {
      "code": "<code>"
    },
    "name": "cadastre_get_licence"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses that duplicate codes return all records with no selection made for the caller, that the text comes from an OCR'd scanned PDF with `anomalies_de_lecture` flagging doubts and nothing corrected, and that the data reflects the edition date and is not authoritative.

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?

Purpose and key semantics are front-loaded, then duplicate handling, then data-provenance caveats — a sensible order. It is slightly long, with the non-authoritative point restated in two consecutive sentences, but almost every sentence carries information.

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?

For a one-parameter read tool with an output schema, the description covers everything an agent needs: how to obtain the code, exact-match requirement, duplicate behavior, and the reliability caveat on the returned data.

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

Parameters5/5

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

Schema coverage is 0% for the single `code` parameter, and the description fully compensates: it defines the code as a stable numeric identifier carried by the published list, requires an exact match, and points to the tool that produces it.

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?

States a specific verb and resource ('Rend le détail d'un titre minier') plus the lookup key ('par son code, l'identifiant numérique que porte la liste publiée'), which cleanly separates it from the sibling search tool that finds such codes.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Pour le trouver, passer par `cadastre_search_licences`', and adds an exclusion ('Ne pas s'en servir pour vérifier un titre sans confirmer auprès de l'autorité citée'), so both the entry condition and the misuse case are stated.

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