Skip to main content
Glama

IA-Asso.fr — French Associations Registry

report_unmet_demand

Report UNMET demand when a precise search did NOT find what the user wanted. Agentic queries are very precise (e.g. "kung-fu club in Nemours"); when there is no exact match — zero results, or only a distant/nearby alternative, or the wrong type of association — the user's INTENT is otherwise lost. Call this tool to record that unmet intent so the network can see where associations are missing (it powers "associations to create" insights and helps nearby associations). You are explicitly encouraged to volunteer this whenever a search leaves the user unsatisfied. No personal data — just the intent, location and theme. Aggregated, welcomed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoShort reason it was unsatisfying (optional)
queryYesThe precise unmet intent, as the user expressed it (e.g. "kung-fu club in Nemours")
themeNoActivity/theme, if known (e.g. "martial arts")
communeNoTargeted commune/city, if known (e.g. "Nemours")
departmentNoTargeted department code, if known (e.g. "77")
nearest_foundNoWhat the search returned instead, if any (e.g. "a club in Fontainebleau, ~12 km")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses no personal data, aggregated use, and that data powers insights. Does not detail auth needs or rate limits, but sufficient for a low-risk tool.

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?

Description is well-structured with a clear first sentence. Slightly verbose with explanatory paragraphs, but every sentence adds value. Could be trimmed without losing meaning.

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?

Given no output schema, the description explains data usage and aggregation. For a simple logging tool, it covers intent, usage, and data handling adequately.

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 baseline is 3. Description provides extra context for parameters (e.g., 'precise unmet intent'), but parameter descriptions in schema are already clear. No added semantic value beyond what schema offers.

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 clearly states the tool's purpose: recording unmet demand when a precise search fails. It specifies the verb 'Report' and the resource 'UNMET demand', and distinguishes it from siblings like search_associations by focusing on intent capture.

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?

Explicit usage context: when precise search yields zero results, distant alternatives, or wrong type. Encourages volunteering. Lacks explicit when-not-to-use or alternatives, but the context is clear enough for an AI agent.

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