Skip to main content
Glama

Unlock Full Official Record by Reference

get_tender_detail
Read-onlyIdempotent

Retrieve the complete unredacted official tender record—full names, tax IDs, verbatim text and document URLs—for a screened item, using the dx_ item_ref returned by a prior search or risk-check tool.

Instructions

Unlock the complete, unredacted official record—including full company and contracting authority names, corporate tax IDs, official document ID (boe_id), verbatim text, and official PDF/HTML/XML URLs—for $0.50 USDC or EURC per call via DATAX_TOKEN (returns HTTP 402 if unset). Requires an opaque item_ref ('dx_...') returned by search_tenders, find_funded_companies, find_distressed_auctions, or check_company_risk. Always run one of those screening tools first to obtain an item_ref.

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": {
      "item_ref": "<item_ref>"
    },
    "name": "get_tender_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_refYesRequired opaque encrypted record handle ('dx_...') obtained from search_tenders, find_funded_companies, find_distressed_auctions, or check_company_risk.

Output Schema

NameRequiredDescriptionDefault
resultNo
statusNo
change_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • addedInput schema / properties / item_ref / description
      Added value: +"Required opaque encrypted record handle ('dx_...') obtained from search_tenders, find_funded_companies, find_distressed_auctions, or check_company_risk."
    • addedInput schema / properties / item_ref / pattern
      Added value: +"^dx_[A-Za-z0-9_-]+$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "change_token": {
      +      "type": "string"
      +    },
      +    "result": {
      +      "properties": {
      +        "boe_id": {
      +          "type": "string"
      +        },
      +        "found": {
      +          "type": "boolean"
      +        },
      +        "item_ref": {
      +          "type": "string"
      +        },
      +        "operation": {
      +          "type": "string"
      +        },
      +        "tender": {
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "status": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the per-call price ($0.50 USDC or EURC), the required auth token (DATAX_TOKEN), the 402 failure response, and the redaction removal that distinguishes this paid detail call from free screening. Annotations already cover read-only/non-destructive safety, and the description adds the commercial and auth context they cannot express.

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?

Two sentences, front-loaded with the payoff (what the full record contains) before the prerequisite. The item_ref provenance is restated from the schema description, a small redundancy, but no sentence is wasted.

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 one-parameter paid detail lookup with an output schema and full annotation coverage, nothing an agent needs is missing: price, auth, error behavior, prerequisite chain, and returned field list are all present, so the output schema need not be explained.

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 already 100% for the single item_ref parameter, so the baseline is 3. The description adds provenance meaning—enumerating the four tools that mint a 'dx_...' handle—which tells the agent where a valid value can come from, though it does not add format or validation detail beyond the schema's pattern.

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 ('Unlock the complete, unredacted official record') and enumerates exactly what is returned (company/authority names, tax IDs, boe_id, verbatim text, PDF/HTML/XML URLs). This clearly separates it from the screening siblings, which return only references.

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?

Gives an explicit prerequisite: run search_tenders, find_funded_companies, find_distressed_auctions, or check_company_risk first to obtain an item_ref. It also states the cost model and the failure mode (HTTP 402 if DATAX_TOKEN is unset), so an agent knows both when to call it and when it will fail.

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