Skip to main content
Glama

caritatif.fr – French Charities & Nonprofits

Rechercher des guides

search_guides
Read-onlyIdempotent

Searches Caritatif.fr editorial guides about donating in France (choosing a reliable charity, tax deduction of donations, charity labels). Use it when a user asks how to give, how tax relief works or what a label means; then call get_guide with a returned slug. Case-insensitive substring match on title, summary and category; with no arguments it returns all guides. Returns results[] (slug, title, summary, category, cause_links, url) and total. 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": "search_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
causeNoOptional cause slug from list_causes to keep only guides linked to that cause (e.g. 'sante').
queryNoFree-text keyword in French, matched against title/summary/category (e.g. 'fiscal', 'label', 'choisir'). Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / cause / description
      Added value: +"Optional cause slug from list_causes to keep only guides linked to that cause (e.g. 'sante')."
    • addedInput schema / properties / cause / examples
      Added value: +[
      +  "environnement"
      +]
    • addedInput schema / properties / query / description
      Added value: +"Free-text keyword in French, matched against title/summary/category (e.g. 'fiscal', 'label', 'choisir'). Optional."
    • addedInput schema / properties / query / examples
      Added value: +[
      +  "fiscal"
      +]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/closed-world, and the description adds real behavioral context beyond them: case-insensitive substring matching over title, summary and category, and the fallback of returning all guides when no arguments are supplied. It also discloses the result shape (results[] with slug, title, summary, category, cause_links, url, plus total), which matters because no output schema exists.

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 purpose, then usage, then matching semantics and return shape; every sentence carries information. It is dense and slightly run-on in the matching/returns sentence, but no clause is filler.

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 two-optional-parameter read-only search with no output schema, the description supplies everything needed: trigger conditions, matching rules, empty-argument behavior, the chained get_guide call, and the return field list. Nothing an agent needs to invoke it 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 100%, so both parameters are already documented, yet the description still adds meaning: it clarifies that the query is a substring match across three specific fields and that the whole parameter set is optional. The cause parameter's linkage to list_causes is left to the schema, so it stops short of a 5.

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 ('Searches Caritatif.fr editorial guides about donating in France') and scopes the content with concrete examples (choosing a reliable charity, tax deduction, labels). It is clearly distinguishable from search_ngos/get_ngo by naming guides as the searched entity and get_guide as the follow-up.

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 explicit trigger conditions ('when a user asks how to give, how tax relief works or what a label means') and an explicit next step ('then call get_guide with a returned slug'). It also states the no-argument default, so the agent knows both when to use it and what happens with empty input.

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