Skip to main content
Glama

caritatif.fr – French Charities & Nonprofits

Classement des associations

top_ngos
Read-onlyIdempotent

Returns the highest-scoring active French associations ranked by Caritatif.fr score (0-100, computed from public registry data: transparency, impact, governance, finances). Use it to shortlist reputable charities for a cause or territory; then call get_ngo for details. All filters are optional and combinable. Returns results[] with slug, name, score, primary_cause, address_city, department_code, address_region. The score reflects public documentation, not an official label. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
causeNoCause slug as returned by list_causes (e.g. 'environnement', 'sante', 'enfance', 'lutte-pauvrete').
limitNoNumber of associations to return (1-50, default 10).
regionNoExact French region name with accents (e.g. 'Île-de-France', 'Auvergne-Rhône-Alpes', 'Occitanie').
department_codeNoFrench département code, 2-3 characters (e.g. '75' Paris, '13' Bouches-du-Rhône, '2A' Corse-du-Sud, '971' Guadeloupe).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / cause / description
      Added value: +"Cause slug as returned by list_causes (e.g. 'environnement', 'sante', 'enfance', 'lutte-pauvrete')."
    • addedInput schema / properties / cause / examples
      Added value: +[
      +  "sante"
      +]
    • addedInput schema / properties / department_code / description
      Added value: +"French département code, 2-3 characters (e.g. '75' Paris, '13' Bouches-du-Rhône, '2A' Corse-du-Sud, '971' Guadeloupe)."
    • addedInput schema / properties / department_code / examples
      Added value: +[
      +  "75"
      +]
    • addedInput schema / properties / department_code / pattern
      Added value: +"^(\\d{2}|2A|2B|\\d{3})$"
    • addedInput schema / properties / limit / default
      Added value: +10
    • addedInput schema / properties / limit / description
      Added value: +"Number of associations to return (1-50, default 10)."
    • addedInput schema / properties / region / description
      Added value: +"Exact French region name with accents (e.g. 'Île-de-France', 'Auvergne-Rhône-Alpes', 'Occitanie')."
    • addedInput schema / properties / region / examples
      Added value: +[
      +  "Île-de-France"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), and the description adds real value on top: how the score is computed (transparency, impact, governance, finances from public registry data) and the caveat that it is 'not an official label'. It omits behavior an agent might still need, such as what happens with zero matches, how ties are broken, or what 'active' means operationally.

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?

Front-loaded with the core action and ranking rationale, and the follow-up pointer plus field list are compact. The returns[] field enumeration is somewhat list-like but earns its place since no output schema exists.

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?

For a filtered-list tool with no output schema, the description covers purpose, scoring semantics, return fields and next step, which is close to self-sufficient. Remaining gaps are the region/department_code precedence rule and edge-case behavior, which are minor for a read-only ranked listing.

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?

Schema description coverage is 100%, so cause, limit, region and department_code are already fully documented, and the description only restates that filters are optional and combinable. It adds no guidance on interaction between filters, e.g. whether region and department_code are ANDed or one overrides the other. Baseline 3 is appropriate when the schema does the heavy lifting.

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 plus the ranking dimension: returns active French associations ordered by the Caritatif.fr score. It also routes away from the detail sibling ('then call get_ngo for details') and the ranking/scoring framing inherently separates it from search_ngos, so an agent can pick it without opening the 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?

Gives a concrete use case ('shortlist reputable charities for a cause or territory') and an explicit follow-up step (get_ngo). It also notes all filters are optional and combinable. It stops short of stating when to prefer search_ngos instead, so the exclusion side is only implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources