Skip to main content
Glama

caritatif.fr – French Charities & Nonprofits

Rechercher des associations

search_ngos
Read-onlyIdempotent

Paginated search of active French associations by name, cause or city, built from official public registries (RNA, SIRENE, JOAFE). Use it to resolve a charity name to its slug, then call get_ngo or get_donation_paths. Returns results[] with slug, name, score, primary_cause, address_city and total. Read-only.

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": {
      "query": "<query>"
    },
    "name": "search_ngos"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number.
limitNoResults per page (1-50).
queryYesName, cause or city in French (min 2 chars).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / limit / default
      Added value: +10
    • addedInput schema / properties / limit / description
      Added value: +"Results per page (1-50)."
    • addedInput schema / properties / page / default
      Added value: +1
    • addedInput schema / properties / page / description
      Added value: +"1-based page number."
    • changedInput schema / properties / query / description
      Previous value: -"Terme de recherche"New value: +"Name, cause or city in French (min 2 chars)."
    • addedInput schema / properties / query / examples
      Added value: +[
      +  "croix rouge"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, and the description adds genuinely new context: the records come from official public registries, only active associations are returned, and results are paginated. The closing "Read-only" merely restates the annotation, and there is no mention of rate limits or ranking behavior behind the score field, so it stops short of a 5.

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

Conciseness5/5

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

Three tight sentences with zero filler: purpose and source first, then the chaining guidance, then the return shape. The return fields (slug, name, score, primary_cause, address_city, total) are folded into one compact clause.

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?

With no output schema, the description usefully enumerates the key response fields and total, and it explains the pagination model. What is missing is a note on how relevance scoring works (results carry a score field), which matters for a search tool where result ordering drives the next step.

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 query, page and limit are already documented in the schema, including the 1-50 limit bound and the min-2-character query rule. The description restates the query dimensions (name, cause or city) but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 with scope: "Paginated search of active French associations by name, cause or city," plus the upstream data sources (RNA, SIRENE, JOAFE). This clearly separates it from siblings like get_ngo, which is a detail lookup rather than a search.

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?

Gives an explicit workflow: resolve a charity name to its slug, then call get_ngo or get_donation_paths. It names the concrete follow-up tools and the condition that motivates each, so the agent knows where this tool sits in a chain.

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