normi

Create Market Alert

create_market_alert

Create a webhook alert for new DVF transactions matching your criteria. Requires Pro or Enterprise plan. Max 20 active alerts per API key.

REQUIRED: webhook_url + at least one location filter (code_postal, commune, or code_departement)

Optional: type_local, prix_min, prix_max, surface_min, surface_max

When a matching transaction is added to DVF, a POST request is sent to your webhook_url with the transaction details.

Cost: 0 credits (Pro/Enterprise plan required)

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": {
      "webhook_url": "<webhook_url>"
    },
    "name": "create_market_alert"
  }
}

Input Schema

Name	Required	Description
`commune`	No	Commune filter in uppercase (e.g., 'PARIS 11').
`prix_max`	No	Maximum price in euros.
`prix_min`	No	Minimum price in euros.
`type_local`	No	Property type filter.
`code_postal`	No	Postal code filter. At least one location filter required.
`surface_max`	No	Maximum surface in m².
`surface_min`	No	Minimum surface in m².
`webhook_url`	Yes	HTTPS URL that will receive POST notifications
`code_departement`	No	Department code filter.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the plan entitlement, a hard quota (20 active alerts per API key), the delivery mechanism (POST to webhook_url with transaction details when a matching DVF transaction appears), and a cost of 0 credits. These are operational facts an agent cannot derive from readOnlyHint=false / idempotentHint=false / openWorldHint=true.

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?

Front-loaded with the purpose, then required constraints, then optional filters, then side effects and cost, in short scannable lines. Every line carries actionable information with no redundant restatement of the name or title.

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?

There is no output schema, but the description explains the observable outcome of the call — a POST payload sent to the webhook on each matching transaction — so the agent knows what to expect. Combined with the quota, plan gate, and filter requirement, nothing needed to invoke this mutation 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 the baseline is 3, but the description adds a cross-field constraint the schema does not encode: webhook_url plus at least one of code_postal, commune, or code_departement. That 'at least one location filter' rule is genuinely new semantics, though the optional filters are only listed by name.

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 — 'Create a webhook alert for new DVF transactions matching your criteria' — and immediately scopes it to alerting on newly added transactions. The verb alone separates it from list_market_alerts, update_market_alert, and delete_market_alert siblings without any ambiguity about what gets created.

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 concrete preconditions an agent must check before calling: Pro/Enterprise plan required, max 20 active alerts per API key, and at least one location filter mandatory. It does not explicitly name alternatives such as update_market_alert for modifying an existing alert, so the agent must infer that from sibling names rather than from this text.

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

All normi 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?