Skip to main content
Glama

A company's public contract awards

company_contracts
Read-onlyIdempotent

List a company's public contract awards, ordered by publication date, newest first: the REST API's GET /v1/companies/{slug}/contracts.

Use it for one company's awards; a name is searched as in company_history: several matches return {ambiguous: true, candidates}, none returns {error, suggested_companies}.

Returns JSON {company_slug, nif, count, offset, next_offset, contracts: [{source, award_id, published, awarded_on, buyer, title, lot, amount_eur, cpv, notice_url, minor}], sources}. Awards come from Spanish and EU public procurement notices, matched by tax ID; awards published in multiple notices are listed once. nif null means we hold no tax ID for the company, not that it won nothing; count 0 is not proof it never won a contract. Legal-entity winners only; TED notices in the pre-eForms format (January-June 2024) are not included.

Read-only; one request per call. Requires the Basic plan or higher and an API key in the X-API-Key header (https://bormeapi.com/account).

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": {
      "company": "<company>"
    },
    "name": "company_contracts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAwards per page, integer 1-200, e.g. 20 (default 50).
offsetNoAwards to skip, integer 0-10000 (default 0); pass the previous page's next_offset, e.g. 50.
sourceNoOptional, one or more of placsp, navarra, ted separated by commas, e.g. ted; omit for all.
companyYesCompany slug as returned by search_companies or company_history (e.g. vaz-metales-sl), or a name to search.
date_toNoOptional latest publication date, YYYY-MM-DD, e.g. 2024-12-31.
date_fromNoOptional earliest publication date, YYYY-MM-DD, e.g. 2024-01-01.
min_amountNoOptional minimum award amount in EUR, e.g. 100000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/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 still adds substantive behavior: auth and plan requirements, one-request-per-call, deduplication of awards across notices, legal-entity-only scope, and the pre-eForms TED gap. The null-nif and zero-count caveats are exactly the kind of interpretation guidance the agent cannot get from annotations.

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?

Front-loaded with the core action, then progressively narrower details (semantics, return shape, caveats, access). Dense but every sentence carries information; the inline endpoint path is slight redundancy with the stated purpose.

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?

With no output schema, the description fully documents the return object and its item fields, plus offsets for pagination and the sources list. Coverage gaps, edge cases, and access prerequisites are all present, which is everything an agent needs for a 7-parameter, paged read tool.

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 baseline is 3; the description earns an extra point by explaining pagination flow (pass the previous page's next_offset) and the dual slug-or-name behavior of the company parameter with its ambiguous/error return shapes. It does not add syntax details for date_from/date_to or source, which the schema already covers.

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 (list public contract awards) with explicit ordering (publication date, newest first) and even names the underlying endpoint GET /v1/companies/{slug}/contracts. The scoping phrase 'Use it for one company's awards' separates it from aggregate or search-style siblings at a glance.

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?

It clearly frames the use case ('for one company's awards') and explains how the company argument resolves names versus slugs, including the ambiguous/error fallbacks. It stops short of naming an alternative tool (e.g. company_grants for subsidies) or stating when not to use it, so it stops at clear context rather than a full routing rule.

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.