editalmd

Create an alert

create_alert

An alert for new procurements by object terms and state (UF). Use the account session or guest token. Channels: pull, signed webhook or email. On webhook and email, it also delivers new tenders outside PNCP that have not opened yet (TCE-RS LicitaCon and TCE-PE open data). Name, organization and email recipients are optional. Two modes. By termos: a space requires all groups; | accepts alternatives within a group. By cnpj: known activity families produce alerts, up to max_familias. Unmapped activities remain in the response without an alert. The cron checks every 30 minutes. Email requires an account session and EMAIL_ALERTAS=1. It uses explicit recipients or the verified account email.

Input Schema

Name	Required	Description	Default
`uf`	No	State (UF) abbreviation (optional).
`nome`	No	Alert name, up to 100 characters.
`canal`	No	pull, webhook or email (default pull).	pull
`termos`	Yes	Object words, 3 to 200 letters; a space means all, \| means any (uniforme\|fardamento).
`destino`	No	HTTPS webhook URL. Ignored for pull and email.
`filtros`	No	Extra filter: modalities, municipalities, exclusions, values, open proposals and CNAEs. PATCH replaces the whole filter; {} clears it.
`resultados`	No	Also deliver the result of each matching purchase when PNCP publishes it, on the same channel: the purchase comes back once with `resultado` (awarded value, items, date and the three largest winners). It starts when turned on, without past results. `abertas` does not apply to results.
`destinatarios`	No	Email recipients: `para`, `cc` and `bcc` arrays. Up to 10 distinct addresses in total. An empty `para` list uses the account email. PATCH replaces all three lists. BCC is hidden from other recipients.
`organizacao_id`	No	Organization from `GET /api/me/empresas`. Membership and MFA are checked. Null removes the label. This does not share alert ownership.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedNov 5, 2026

addedInput schema / properties / destinatarios / properties / bcc / description

Added value: +"Hidden copy addresses. Only the alert owner can read this list."

addedInput schema / properties / destinatarios / properties / cc / description
```
Added value: +"Visible copy addresses."
```
addedInput schema / properties / destinatarios / properties / para / description
```
Added value: +"To addresses. An empty list uses the verified account email."
```

addedInput schema / properties / filtros / properties / abertas / description

Added value: +"Require the proposal deadline to be open at collection time."

addedInput schema / properties / filtros / properties / cnaes / description

Added value: +"Up to 8 CNAE subclasses, such as 4644301 or 4644-3/01. Matches one of the purchase's three most likely CNAEs."

addedInput schema / properties / filtros / properties / disputa / description

Added value: +"Only purchases with competitive bidding. Excludes PNCP's not-applicable bidding mode."

addedInput schema / properties / filtros / properties / esferas / description

Added value: +"Government spheres: F federal, E state, D district and M municipal. Records without a sphere are excluded."

addedInput schema / properties / filtros / properties / excluir / description

Added value: +"Up to 10 literal phrases, each 3–80 characters, to exclude from the purchase subject."

addedInput schema / properties / filtros / properties / modalidades / description
```
Added value: +"Up to 10 PNCP procedure codes, from 1 to 19."
```

addedInput schema / properties / filtros / properties / municipios / description

Added value: +"Up to 10 exact municipality names or IBGE codes. Use UF to distinguish names."

addedInput schema / properties / filtros / properties / srp / description

Added value: +"Only purchases marked as price registration (srp) by PNCP."

addedInput schema / properties / filtros / properties / valor_max / description
```
Added value: +"Maximum estimated value in Brazilian reais."
```
addedInput schema / properties / filtros / properties / valor_min / description
```
Added value: +"Minimum estimated value in Brazilian reais."
```

Changed4 schema fields changedOct 31, 2026

addedInput schema / properties / filtros / properties / disputa
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / filtros / properties / esferas

Added value: +{
+  "items": {
+    "enum": [
+      "F",
+      "E",
+      "D",
+      "M"
+    ],
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}

addedInput schema / properties / filtros / properties / srp
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / resultados

Added value: +{
+  "description": "Also deliver the result of each matching purchase when PNCP publishes it, on the same channel: the purchase comes back once with `resultado` (awarded value, items, date and the three largest winners). It starts when turned on, without past results. `abertas` does not apply to results.",
+  "type": "boolean"
+}

Changed4 schema fields changedOct 17, 2026

addedInput schema / properties / destinatarios

Added value: +{
+  "additionalProperties": false,
+  "description": "Email recipients: `para`, `cc` and `bcc` arrays. Up to 10 distinct addresses in total. An empty `para` list uses the account email. PATCH replaces all three lists. BCC is hidden from other recipients.",
+  "properties": {
+    "bcc": {
+      "items": {
+        "format": "email",
+        "maxLength": 254,
+        "type": "string"
+      },
+      "maxItems": 10,
+      "type": "array"
+    },
+    "cc": {
+      "items": {
+        "format": "email",
+        "maxLength": 254,
+        "type": "string"
+      },
+      "maxItems": 10,
+      "type": "array"
+    },
+    "para": {
+      "items": {
+        "format": "email",
+        "maxLength": 254,
+        "type": "string"
+      },
+      "maxItems": 10,
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

changedInput schema / properties / destino / description

Previous value: -"https URL (webhook); ignored for pull and email (email goes to the account e-mail)."New value: +"HTTPS webhook URL. Ignored for pull and email."

addedInput schema / properties / nome

Added value: +{
+  "description": "Alert name, up to 100 characters.",
+  "maxLength": 100,
+  "type": "string"
+}

addedInput schema / properties / organizacao_id

Added value: +{
+  "description": "Organization from `GET /api/me/empresas`. Membership and MFA are checked. Null removes the label. This does not share alert ownership.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

AddedOct 15, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Beyond the annotations it discloses the 30-minute cron cadence, the fact that webhook and email channels also push non-PNCP tenders (TCE-RS LicitaCon, TCE-PE), and that unmapped activities come back in the response without an alert. It still omits what happens on duplicate creation and whether plan/quota limits gate creation.

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

Conciseness3/5

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

Purpose and channel behaviour are front-loaded, which is good, but the prose is telegraphic and fragmentary ("Two modes.", "The cron checks every 30 minutes.") and repeats schema content about `termos`. The `cnpj`/`max_familias` sentences are dead weight for this tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter tool with nested objects and no output schema, the description covers auth, channel delivery and side effects but says nothing about what is returned (alert id, created record) or how failures surface. The nested `filtros` and `destinatarios` behaviour is carried entirely by the schema.

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 the baseline is 3. The description restates the `termos` space/pipe semantics that the schema already documents and calls out name, organization and recipients as optional, but adds no new detail for the nine parameters; the stray `max_familias` reference points at a parameter that does not exist here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition makes clear it sets up a standing alert for new procurements filtered by object terms and UF, and it names the delivery channels. It blurs the boundary with the sibling `create_alerts_by_cnpj` by describing a `cnpj` mode ("up to `max_familias`") that has no corresponding parameter in this tool's schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives real prerequisites: account session or guest token, and email requires a session plus `EMAIL_ALERTAS=1`. What it does not do is route between siblings — there is no statement about when to use this versus `preview_alert`, `update_alert`, or `create_alerts_by_cnpj`, so the agent must infer the choice.

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

All editalmd 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.

Create an alert

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources