Skip to main content
Glama

Company public funding

company_public_funding
Read-onlyIdempotent

Public grants and state aid one company received, from the EU State aid Transparency Award Module, Kohesio and the Financial Transparency System, with totals per year and per programme. Takes node_id, the graph node id from search_companies hits. Each award cites its source record and states how it was bound to the company, always by an identifier and never by a name alone. Totals never add figures of a different basis or currency, and a range a source states stays a range (band_low_total and band_high_total). The tool reads only awards to organisations. State aid figures from TAM are aid granted, not aid paid, published only above the threshold of each measure and never for de minimis aid, and for a loan or a guarantee a figure may be the loan or guarantee itself.

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": {
      "node_id": "<node_id>"
    },
    "name": "company_public_funding"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_idYesThe graph node id, as returned by search_companies hits. Not the entity_id of company_profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / node_id / maximum
      Added value: +2147483647
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial behavioural detail beyond them: award provenance and citation, the guarantee that binding is by identifier and never by name alone, the aggregation rule that totals never mix bases or currencies, preservation of ranges as band_low_total/band_high_total, and the critical caveat that TAM figures are aid granted (not paid), above threshold, excluding de minimis, and may represent the loan or guarantee itself. This is exactly the kind of non-obvious semantics an agent cannot get from the schema.

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?

It is front-loaded with the resource and sources before moving into caveats, and every sentence carries information an agent could act on. It is dense and on the long side, but the length is justified by the number of distinct data-semantics warnings; little is padded.

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, so the description carries the burden of describing returns — and it does: per-year and per-programme totals, source citations, binding method, and range representation via band_low_total/band_high_total. Combined with the annotation coverage of the safety profile and a fully documented single parameter, an agent has everything needed to call this correctly.

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?

With one parameter and 100% schema coverage, the baseline is 3; the description earns above that by clarifying the identifier's origin (graph node id from search_companies hits) and explicitly warning against the plausible mistake of passing company_profile's entity_id. It adds genuine disambiguation rather than repeating the schema text.

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 description names a specific resource (public grants and state aid received by one company) and enumerates its sources (TAM, Kohesio, Financial Transparency System) plus the shape of what comes back (totals per year and per programme). That is far more specific than a restatement of the title. It stops short of explicitly separating itself from adjacent siblings such as company_financing or company_financials, so an agent still has to infer which funding-flavoured tool applies.

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 does give one concrete usage instruction — node_id comes from search_companies hits — and rules out a wrong-looking alternative ('Not the entity_id of company_profile'). It also narrows scope with 'reads only awards to organisations'. However, there is no statement of when to reach for this tool versus company_financing, company_financials or company_overview, so alternative selection is left implied.

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