Skip to main content
Glama

Append Company Data

append-data
Read-onlyIdempotent

Use when the user has 2+ domains to enrich with firmographics, growth trends, redirects, vendor/technology domains, subdomains, or domain status — the bulk enrichment tool.

This tool enriches up to 1000 domains per call. Domains can be passed directly, resolved from a saved query via query_id, or both — the resulting domain lists are unioned.

Each dataset adds different fields to the results. Select which datasets to include.

Response shape

Each result row is keyed by 'domain'. Every requested dataset's fields are nested under an object named after the dataset — there are no flattened 'dataset:field' keys. A dataset whose data is a single field (e.g. vendors) collapses to that value directly. A dataset is omitted for a domain when no data is found.

Example (dataset=['bizdata','vendors']): {"domain": "stripe.com", "bizdata": {"name": "Stripe", "employees": "10001+"}, "vendors": ["apple.com", ...]}

The optional 'fields' parameter selects whole top-level keys: 'domain' plus any requested dataset name (e.g. fields=['domain','vendors']). The lists below document what each nested object contains.

Dataset: bizdata

domain, name, status, score, start_date, end_date, address, latitude, longitude, geo_precision, phones, public_emails, domain_associations, social_urls, redirect_domain, description, keywords, industry_groups, sub_industry, employees, revenue_range, business_model, update_date, mx_provider, linkup. Field details: https://docs.discolike.com. score: Digital footprint score derived from certificate history (1-800); not a verified measure of company size or buying power start_date: First observed certificate date (YYYY-MM-DD); not a verified company founding or incorporation date . Field details: https://docs.discolike.com.

Dataset: redirects

redirect_sources, redirect_count. Field details: https://docs.discolike.com.

Dataset: domain_status

status_code, status_reason, record_date. Field details: https://docs.discolike.com.

Dataset: growth

score_growth_3m, subdomain_growth_3m. Field details: https://docs.discolike.com. Note: growth also includes dynamic quarterly fields (score_YYYYQX, subdomains_YYYYQX).

Dataset: vendors

vendors. Field details: https://docs.discolike.com.

Dataset: subdomains

subdomains. Field details: https://docs.discolike.com.

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": {
      "filters": "<filters>"
    },
    "name": "append-data"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoTop-level response keys to include: 'domain' plus any requested dataset name (e.g. ['domain','vendors']). Sub-fields cannot be selected — each dataset's fields are always returned nested under the dataset name.
formatNoResponse format: rows or columnarrows
contextNoWhy you are calling this tool, in a few words. No names or emails.
filtersYesInput filters for the append MCP tool.
llm_modelNoYour model id, or "unknown".
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
countNo
resultsNo
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / properties
      Added value: +{
      +  "_mcp_instructions": {
      +    "description": "Server-issued metadata for this conversation.",
      +    "properties": {
      +      "conversation_id": {
      +        "description": "The server-issued conversation identifier.",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "count": {
      +    "type": "integer"
      +  },
      +  "results": {
      +    "anyOf": [
      +      {
      +        "items": {
      +          "additionalProperties": true,
      +          "required": [],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      {
      +        "additionalProperties": {
      +          "items": {},
      +          "type": "array"
      +        },
      +        "required": [],
      +        "type": "object"
      +      }
      +    ]
      +  }
      +}
    • addedOutput schema / required
      Added value: +[]
  2. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Why you are calling this tool, in a few words. No names or emails.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Your model id, or \"unknown\".",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations declare readOnly/idempotent/non-destructive, and the description still adds substantial operational detail beyond them: a 1000-domain cap per call, the union semantics when domains and query_id are both supplied, and the rule that a dataset is omitted for a domain with no data. The response-shape explanation (nested per-dataset objects, single-field datasets collapsing to a value) is behavioral information an agent would otherwise have to discover by trial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The usage line is correctly front-loaded and the '## Response shape' section is well organized, but the description is bloated by repeating '. Field details: https://docs.discolike.com.' after every dataset and leaving a stray sentence fragment before another repeated link in the bizdata block. The dataset enumeration is necessary; the boilerplate is not.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter enrichment tool with nested filters and a real output schema, the description covers the inputs, the limits, and the merge semantics well. The only shortfall is that field-level documentation is deferred to an external URL, so an agent cannot fully resolve what a given nested field contains from the description alone.

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 schema coverage at 100%, the schema already documents domains, query_id, fields, and format. The description still adds real meaning: it explains that dataset lists are unioned, that 'fields' selects only whole top-level keys, and it documents the contents and caveats of each dataset (e.g. score is a certificate-derived footprint score, not a size measure). The repeated external docs links are pointers rather than explanations.

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 opening sentence states a concrete verb (bulk enrichment) and enumerates the resource dimensions covered (firmographics, growth, redirects, vendors, subdomains, domain status), and the phrase 'the bulk enrichment tool' plus the '2+ domains' threshold implicitly separates it from single-domain lookups. It never names a sibling tool outright, so differentiation is scope-based rather than explicit.

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?

'Use when the user has 2+ domains to enrich' gives a clear triggering condition and the bulk-vs-single boundary is implied by the domain count. What is missing is an explicit pointer to the alternative for one-off lookups or non-enrichment tasks, and no guidance on choosing datasets for a given user intent.

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