Skip to main content
Glama

Export companies to CSV (AT + DE)

export_companies_csv
Read-only

Beispiel: „Alle Steuerberatungskanzleien in Wien als CSV exportieren?“

Export a matched company set as downloadable CSV files (lead lists). Read-only over company data; each call writes new short-lived export files (auto-deleted after ~1 day).

    Parameters:
    - filters (optional): EXACTLY the same unified filters as search_companies.
    - sort (optional): same as search_companies (applies where the country supports
      the field).
    - max_rows (optional, default 1000, max 10000): per-country row ceiling.
    - country (optional, default "all"): "AT" | "DE" | "all".

    Returns {countries: {<code>: {download_url, rows, columns, ...}}, notices}. ONE
    CSV per country (semicolon-separated, UTF-8 BOM, Excel-ready): each register
    exports its own column set - DE files have no financial columns yet (blank would
    wrongly read as zero). Download links are signed and valid ~60 minutes. A filter a
    country does not support excludes that country with a notice, like
    search_companies. For browsing/ranking on screen use search_companies instead.

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": "export_companies_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
countryNoall
filtersNo
max_rowsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed23 schema fields changed
    • addedInput schema / $defs / UnifiedSearchFilters / additionalProperties
      Added value: +false
    • changedInput schema / $defs / UnifiedSearchFilters / description
      Previous value: -"Every field optional, AND-combined. A filter a country does not support excludes\nthat country from a country=\"all\" fan-out (with an explicit notice); on an explicit\nsingle-country query it is rejected with the capability notice instead."New value: +"Every field optional, AND-combined. A filter a country does not support excludes\nthat country from a country=\"all\" fan-out (with an explicit notice); on an explicit\nsingle-country query it is rejected with the capability notice instead.\n\nA filter NAME this model does not declare is rejected (``extra=\"forbid\"`` plus the\nbefore-validator below, which names the offender and points to ``describe_fields``). Until\n2026-11-16 pydantic's default ``extra=\"ignore\"`` dropped it silently: a client that sent\n``family_successor: false`` through the facade got the unfiltered list and no notice, the\nexact \"shorter list under a label that claims the filter\" the data-consistency rule forbids."
    • addedInput schema / $defs / UnifiedSearchFilters / properties / anlagevermoegen_max
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Anlagevermoegen Max"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / anlagevermoegen_min
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Anlagevermoegen Min"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / any_officer_age_min
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Any Officer Age Min"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / bezirk
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Bezirk"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / ebit_margin_max
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Ebit Margin Max"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / ebit_margin_min
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Ebit Margin Min"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / ebit_max
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Ebit Max"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / ebit_min
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Ebit Min"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / ebitda_max
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Ebitda Max"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / ebitda_min
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Ebitda Min"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / exclude_cities
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Exclude Cities"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / exclude_geschaeftszweig_terms
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Exclude Geschaeftszweig Terms"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / exclude_legal_form
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Exclude Legal Form"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / exclude_name_terms
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Exclude Name Terms"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / exclude_oenace
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Exclude Oenace"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / exclude_postal_codes
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Exclude Postal Codes"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / family_successor
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Family Successor"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / family_successor_gap_min
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Family Successor Gap Min"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / jahresueberschuss_max
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Jahresueberschuss Max"
      +}
    • addedInput schema / $defs / UnifiedSearchFilters / properties / jahresueberschuss_min
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Jahresueberschuss Min"
      +}
    • changedInput schema / $defs / UnifiedSearchFilters / properties / status / enum
      Previous value: -[
      -  "active",
      -  "inactive",
      -  "all"
      -]New value: +[
      +  "active",
      +  "operating",
      +  "inactive",
      +  "all"
      +]
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations mark it read-only/non-destructive, and the description adds behavior annotations cannot express: each call writes new short-lived files auto-deleted after ~1 day (which explains idempotentHint=false), signed download links expire after ~60 minutes, and DE files intentionally omit financial columns to avoid blank-reads-as-zero. That is exactly the extra context the lower bar for annotated tools asks for.

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 purpose, then behavior, then a tight parameter list, then return shape and the alternative — a sensible order with no filler sentences. The opening German example question is illustrative but not load-bearing, and the stray line breaks cost it a point.

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 62-field filter object with cross-country fan-out semantics, the description covers side effects, per-country column differences, expiry windows, notices, and the returns shape. With an output schema present it does not need to enumerate return values further, and nothing an agent needs 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.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage the description carries the burden and does: filters and sort are defined by reference to search_companies, max_rows is given a default (1000) and a max (10000) and clarified as per-country, and country is given a default plus its allowed values. It adds meaning the raw schema does not.

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 ('Export a matched company set as downloadable CSV files (lead lists)') plus the scope ('AT + DE' in the title, country param). The closing line explicitly separates it from the sibling search_companies, so an agent can route between them without opening either 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?

Gives an explicit when-not: 'For browsing/ranking on screen use search_companies instead', and explains the fan-out rule (a filter a country does not support excludes that country with a notice) versus the single-country rejection case in the schema. Both the right tool and the right failure expectation are named.

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.