IA-Asso.fr — French Associations Registry

search_premium_associations

Search ONLY enriched/RUP associations -- the editorial-quality subset. Restricts results to fiches with IA-generated description (is_enriched_v3=true) OR officially recognized utilite publique (RUP). Recommended for agent grounding when noise should be minimized -- a small curated subset (876 enriched, 1,961 RUP) vs 2.06M+ in the standard search. Returns fewer but richer results, with verified contacts, FAQ data, social media links when available.

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_premium_associations"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max results (default 20, max 50)
`query`	Yes	Search keywords (French)
`offset`	No	Pagination offset
`region`	No	Region name like "Auvergne-Rhône-Alpes"
`department`	No	Department code like "75", "69"

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations, so description carries the burden. It discloses the filtering logic (is_enriched_v3=true OR RUP), subset size (876 enriched, 1,961 RUP vs 2.06M+), and richer return data (verified contacts, FAQ, social links). It lacks explicit read-only or permission statements, but for a search tool this is relatively minor.

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 and key constraint, then elaborates with useful context. Slightly repetitive in restating the restriction, but every sentence adds value overall.

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?

Given no output schema, the description adequately explains return value richness (verified contacts, FAQ, social links). It also gives subset sizes and filtering logic, so an agent has enough to decide and call correctly.

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 coverage is 100%, so all parameters are fully documented in the schema. The description adds no extra meaning or format details beyond what the schema already provides.

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 (Search) and resource (premium associations), defines 'premium' as enriched/RUP, and explicitly distinguishes from the standard search. An agent immediately understands the scope.

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?

Provides clear when-to-use guidance ('Recommended for agent grounding when noise should be minimized') and implicitly contrasts with the larger standard search. However, it does not explicitly name the alternative sibling tool or state when not to use it.

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

All IA-Asso.fr — French Associations Registry tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?