Skip to main content
Glama

editalmd

by com.editalmd
OverviewDiscussionsAdmin

Search tenders

search_tenders
Read-onlyIdempotent

Searches public procurements by term. Free. Returns the object, the agency, the state (UF), the modality and the procurement id. The procurements that receive proposals now come first, then the most recently published ones. With ordem 'prazo', the one that closes first comes first.

Input Schema

NameRequiredDescriptionDefault
qYesSearch term, at least 3 letters. When no procurement has all the words, it returns the ones with some of them (todas_as_palavras: false).
ufNoState (UF) abbreviation (optional).
ordemNo'prazo' to put first the procurement that closes first; only with abertas '1'.
limiteNo1 to 50 (default 20).
abertasNo'1' for only procurements with an open proposal period, without the ones PNCP shows as revoked or annulled.
filtrosNoJSON up to 2048 characters: excluir and municipios (up to 10 expressions of 3 to 80 characters; municipalities by exact name or IBGE code), orgao_cnpj (14 digits), modalidades (up to 10 codes from 1 to 19), disputa (true: only purchases with bidding; with modality 8, direct purchases with bidding), srp (true: only procurements under the Price Registration System), esferas (F, E, D, M: federal, state, Federal District, municipal), valor_min and valor_max (reais from 0 to 1e15), encerramento_de and encerramento_ate (YYYY-MM-DD day of the proposal deadline), publicacao_de and publicacao_ate (YYYY-MM-DD day of the publication on PNCP). Example: {"excluir":["usado"],"modalidades":[6]}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / abertas / description
      Previous value: -"'1' for only procurements with an open proposal period."New value: +"'1' for only procurements with an open proposal period, without the ones PNCP shows as revoked or annulled."
    • changedInput schema / properties / filtros / description
      Previous value: -"JSON up to 2048 characters: excluir and municipios (up to 10 expressions of 3 to 80 characters; municipalities by exact name or IBGE code), orgao_cnpj (14 digits), modalidades (up to 10 codes from 1 to 19), valor_min and valor_max (reais from 0 to 1e15). Example: {\"excluir\":[\"usado\"],\"modalidades\":[6]}."New value: +"JSON up to 2048 characters: excluir and municipios (up to 10 expressions of 3 to 80 characters; municipalities by exact name or IBGE code), orgao_cnpj (14 digits), modalidades (up to 10 codes from 1 to 19), disputa (true: only purchases with bidding; with modality 8, direct purchases with bidding), srp (true: only procurements under the Price Registration System), esferas (F, E, D, M: federal, state, Federal District, municipal), valor_min and valor_max (reais from 0 to 1e15), encerramento_de and encerramento_ate (YYYY-MM-DD day of the proposal deadline), publicacao_de and publicacao_ate (YYYY-MM-DD day of the publication on PNCP). Example: {\"excluir\":[\"usado\"],\"modalidades\":[6]}."
    • addedInput schema / properties / ordem
      Added value: +{
+  "description": "'prazo' to put first the procurement that closes first; only with abertas '1'.",
+  "enum": [
+    "prazo"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / q / description
      Previous value: -"Search term, at least 3 letters."New value: +"Search term, at least 3 letters. When no procurement has all the words, it returns the ones with some of them (todas_as_palavras: false)."
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish the safe read-only, idempotent profile, and the description adds genuinely new behavioral information: the result ordering rules (open-for-proposals first, then most recently published; with 'prazo', earliest closing first) and that the call is free. It stops short of describing result volume or empty-result behavior, which limits it to a 4.

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?

Four tight sentences with the core purpose front-loaded and no filler. The return-field sentence is slightly list-like but earns its place as the only description of output shape, since no output schema exists.

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?

With six parameters, full schema coverage, and no output schema, the description covers purpose, cost, ordering, and the returned fields — enough to call and interpret the tool. Empty-result behavior and any total-count/pagination semantics are the remaining gaps.

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 description coverage is 100%, so parameter meaning is already fully documented, and the description adds little parameter-level detail beyond reiterating the 'ordem prazo' interaction. Baseline 3 applies because the schema does the heavy lifting 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?

States a specific verb and resource ('Searches public procurements by term') and scopes it with 'Free', which separates it from the by-id lookup (get_procurement) and the coverage siblings (tenders_outside_pncp, open_tenders_in_field). It doesn't explicitly name those alternatives, so an agent still has to infer the division of labor.

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?

The framing 'by term' plus the note that 'ordem prazo' requires abertas '1' implies the intended query patterns, but there is no explicit statement of when to choose this over get_procurement or the field/outside-PNCP variants. Usage is implied rather than stated.

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

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