Skip to main content
Glama

Screen Companies Receiving Grants, Awards, or Capital

find_funded_companies
Read-onlyIdempotent

Identify companies in Italy receiving government grants, public contracts, or capital raises above an EUR threshold; filter by region, sector, event type, and minimum amount.

Instructions

Identify companies in Italy receiving newly awarded government grants, public procurement contracts, or share-capital raises above an EUR threshold. Costs $0.10 USDC or EURC per call via DATAX_TOKEN (returns HTTP 402 if unset). Returns masked previews with EUR amounts and opaque item_ref handles ('dx_...') to unlock beneficiary identities via get_tender_detail ($0.50). Prefer this over search_tenders when filtering by EUR liquidity thresholds or event_type; use check_company_risk to vet a known company.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_funded_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of funded company leads to return (1 to 25, default 10).
queryNoOptional full-text keywords to filter funded leads by sector, CPV, or activity.
ambitoNoCase-insensitive region, city, or department substring filter (e.g. 'Milano or Roma'). Optional.
event_typeNoLiquidity event category: 'ALL' (default), 'SUBVENCION_SC' (corporate grants), 'ADJUDICACION' (public contract awards), or 'CONSTITUCION_CAPITAL' (incorporations and capital increases).ALL
min_importe_eurNoMinimum grant, contract award, or capital amount in EUR (>= 0, default 0).

Output Schema

NameRequiredDescriptionDefault
resultNo
statusNo
change_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.1.1
    • addedInput schema / properties / ambito / description
      Added value: +"Case-insensitive region, city, or department substring filter (e.g. 'Milano or Roma'). Optional."
    • addedInput schema / properties / event_type / default
      Added value: +"ALL"
    • addedInput schema / properties / event_type / description
      Added value: +"Liquidity event category: 'ALL' (default), 'SUBVENCION_SC' (corporate grants), 'ADJUDICACION' (public contract awards), or 'CONSTITUCION_CAPITAL' (incorporations and capital increases)."
    • addedInput schema / properties / event_type / enum
      Added value: +[
      +  "ALL",
      +  "SUBVENCION_SC",
      +  "ADJUDICACION",
      +  "CONSTITUCION_CAPITAL"
      +]
    • addedInput schema / properties / limit / default
      Added value: +10
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of funded company leads to return (1 to 25, default 10)."
    • addedInput schema / properties / limit / maximum
      Added value: +25
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / min_importe_eur / default
      Added value: +0
    • addedInput schema / properties / min_importe_eur / description
      Added value: +"Minimum grant, contract award, or capital amount in EUR (>= 0, default 0)."
    • addedInput schema / properties / min_importe_eur / minimum
      Added value: +0
    • addedInput schema / properties / query / description
      Added value: +"Optional full-text keywords to filter funded leads by sector, CPV, or activity."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "change_token": {
      +      "type": "string"
      +    },
      +    "result": {
      +      "properties": {
      +        "data_version": {
      +          "type": "string"
      +        },
      +        "event_type": {
      +          "type": "string"
      +        },
      +        "matches": {
      +          "items": {
      +            "properties": {
      +              "ambito": {
      +                "description": "Geographic jurisdiction or region.",
      +                "type": "string"
      +              },
      +              "detail_locked": {
      +                "description": "Always true until unlocked with get_tender_detail.",
      +                "type": "boolean"
      +              },
      +              "fecha_pub": {
      +                "description": "Publication date in YYYYMMDD format.",
      +                "type": "string"
      +              },
      +              "importe_texto": {
      +                "description": "Formatted amount string when available.",
      +                "type": "string"
      +              },
      +              "item_ref": {
      +                "description": "Opaque encrypted record reference ('dx_...') for get_tender_detail.",
      +                "type": "string"
      +              },
      +              "notice_type": {
      +                "description": "Notice classification.",
      +                "type": "string"
      +              },
      +              "preview": {
      +                "description": "Redacted summary preview without PII or entity identifiers.",
      +                "type": "string"
      +              },
      +              "seccion": {
      +                "description": "Registry section code.",
      +                "type": "string"
      +              },
      +              "unlock_price_micros": {
      +                "description": "Unlock price in USD/EUR micros (500000 = 0.50).",
      +                "type": "integer"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "operation": {
      +          "type": "string"
      +        },
      +        "total_returned": {
      +          "type": "integer"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "status": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, and the description adds substantial context beyond them: $0.10 USDC or EURC per call via DATAX_TOKEN, HTTP 402 when unset, masked previews with EUR amounts, and opaque dx_ item_ref handles that require get_tender_detail ($0.50) to unlock identities. That is the paid-access and partial-result behavior an agent needs before invoking.

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?

Three tight sentences, front-loaded with the purpose and followed by cost/auth and routing guidance; no filler. It is dense but each sentence carries distinct information, with only mild compression loss around the pricing mechanics.

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?

For a read-only, open-world search tool with an output schema and fully documented parameters, the description supplies the remaining essentials: price, credential requirement, the masked-preview limitation, and the paid unlock path. Nothing an agent needs in order to call it correctly is missing.

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 the schema already documents limit, query, ambito, event_type, and min_importe_eur. The description reinforces the EUR-threshold and event_type filtering but adds no format, syntax, or interaction detail beyond what the schema supplies, so the baseline of 3 applies.

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 names a specific verb and resource ('Identify companies in Italy receiving newly awarded government grants, public procurement contracts, or share-capital raises') plus the EUR-threshold scoping. It also distinguishes itself from search_tenders and check_company_risk, so an agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

It gives an explicit routing rule: prefer this over search_tenders when filtering by EUR liquidity thresholds or event_type, and use check_company_risk to vet a known company. The condition that selects each alternative is stated, leaving nothing to inference.

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