Skip to main content
Glama
mining-cadastre-mcp

mining-cadastre-mcp

Rechercher des titres miniers

cadastre_search_licences
Read-onlyIdempotent

Search Burkina Faso's published mining titles by code, status, company, or title category; results can be limited and matching ignores case and accents.

Instructions

Recherche des titres miniers dans la liste publiée par l'autorité. Tous les critères sont facultatifs et se combinent ; sans critère, rend le début de la liste. La comparaison ignore la casse et les accents.

ATTENTION sur deux points. Premièrement, la substance exploitée n'est PAS publiée dans ces listes : categorie porte sur la catégorie de titre — permis de recherche, exploitation artisanale, mines contre carrières — et ne permet pas de distinguer l'or du manganèse. Deuxièmement, le texte provient d'un PDF scanné puis océrisé : une valeur mal reconnue peut empêcher un rapprochement. Le champ anomalies_de_lecture signale les enregistrements concernés. Rien n'est corrigé.

La donnée ne fait pas foi et reflète la date d'édition, pas le jour. Le registre officiel est la seule référence opposable.

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": "cadastre_search_licences"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNo
limiteNo
statutNo
societeNo
categorieNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses critical behavioral caveats: the exploited substance is not published, `categorie` refers to title category rather than mineral, OCR errors can prevent matching, and `anomalies_de_lecture` flags affected records. It also states that data is not authoritative and reflects the edition date, not the current day.

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?

The description is structured, front-loads the search behavior, and reserves the warning for the two most important caveats. It is somewhat dense but every sentence carries useful information.

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

Completeness3/5

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

The output schema and annotations cover return values and safety behavior, and the description adds important provenance warnings. However, for a five-parameter search tool with 0% schema description coverage, the missing semantics for most filters leave it incomplete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It explains `categorie` in useful detail and notes case/accent-insensitive matching, but it leaves `code`, `statut`, `societe`, and `limite` essentially undefined.

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 states a specific verb and resource: searching mining titles in the authority's published list. It makes the scope clear enough to distinguish this list-search tool from a detail-fetching sibling such as cadastre_get_licence.

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 explains that all criteria are optional and combinable, and that no criteria returns the beginning of the list. It does not explicitly compare itself with cadastre_get_licence or cadastre_list_jurisdictions, but it gives clear usage context.

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