Skip to main content
Glama

interzoid_enrich_records

Read-onlyIdempotent

Enrich up to 100 records in one call. Send the records as JSON objects (for example [{"id": 1, "company": "Cisco"}, {"id": 2, "company": "Nvidia"}]) and get every record back with the chosen function's output fields appended after its own fields: company profiles, executives, industry codes, email, phone, and IP scoring, tax and duty rates, standardization, custom fields you define, and more. Use this instead of calling a single-record tool once per record. Call interzoid_enrich_functions (free) to see each function's inputs, output fields, and price. Fields named after the function's inputs (usually "lookup") are used automatically; otherwise set lookup_field. Other fields, such as ids, pass through unchanged. Premium functions accept an optional language for results in that language. Cost: the function's price per record times the number of records, from $0.01 to $0.35 per record ($1.00 to $35.00 for 100 records); the x402 payment-required result states the exact total. Check with the user before running premium functions on many records. Functions and price per record (* = accepts language): address-parse $0.01, building-profile $0.25*, business-info $0.25*, business-info-domain $0.10*, business-info-name $0.10*, buying-signals $0.25*, city-standard $0.01, company-verification $0.25*, competitor-analysis $0.25*, country-standard $0.01, custom $0.25*, customs-duty-rates $0.35*, email-domain-type $0.01, email-trust-score $0.25*, entity-type $0.01, esg-profile $0.25*, eu-vat-rates $0.25*, executive-profile $0.25*, facilities-profile $0.25*, gender-from-name $0.01, gov-contracts $0.25*, industry-codes $0.25*, ip-profile $0.25*, irs-per-diem-rates $0.25*, muni-issuer-profile $0.25*, name-origin $0.01, org-standard $0.01, parent-company $0.25*, phone-profile $0.25*, private-company-deal-intel $0.25*, property-history $0.25*, sales-use-tax-rates $0.25*, sic-codes $0.25*, state-standard $0.01, stock-analysis $0.25*, tech-stack $0.25*, translate $0.01, university-info $0.25*, x-handle $0.05*.

Input Schema

NameRequiredDescriptionDefault
topicNofunction=custom only: what the data is about, for example "City statistics".
recordsYes1 to 100 records. JSON objects are recommended, for example [{"id": 1, "company": "Cisco"}]; each comes back with the output fields appended. Plain values (for single-input functions) and arrays of values also work. All records must have the same shape.
functionYesEnrichment function. See interzoid_enrich_functions for inputs, outputs, and prices.
languageNoOptional. Two-letter code for results in that language (premium functions only; default English): fr French, de German, it Italian, es Spanish, ja Japanese, pt Portuguese, zh Mandarin, ar Arabic, nl Dutch, el Greek, tr Turkish, ko Korean, sv Swedish, vi Vietnamese, th Thai, id Indonesian. Same price in every language.
fixed_valuesNoOne value for an input on every record, for example {"to": "Spanish"} for translate.
input_fieldsNoFor functions with several inputs: maps each input name to a record field, for example {"origin": "from_country", "hscode": "hs_code"} for customs-duty-rates. Not needed for fields already named after the inputs.
lookup_fieldNoThe record field that holds the lookup value, for example "company". Not needed when the records have a field named like the input (usually "lookup") or have only one field.
output_fieldsNofunction=custom only: the output field names you want (up to 12), for example ["Population", "Mayor"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / function / enum
      Added value: +[
      +  "address-parse",
      +  "building-profile",
      +  "business-info",
      +  "business-info-domain",
      +  "business-info-name",
      +  "buying-signals",
      +  "city-standard",
      +  "company-verification",
      +  "competitor-analysis",
      +  "country-standard",
      +  "custom",
      +  "customs-duty-rates",
      +  "email-domain-type",
      +  "email-trust-score",
      +  "entity-type",
      +  "esg-profile",
      +  "eu-vat-rates",
      +  "executive-profile",
      +  "facilities-profile",
      +  "gender-from-name",
      +  "gov-contracts",
      +  "industry-codes",
      +  "ip-profile",
      +  "irs-per-diem-rates",
      +  "muni-issuer-profile",
      +  "name-origin",
      +  "org-standard",
      +  "parent-company",
      +  "phone-profile",
      +  "private-company-deal-intel",
      +  "property-history",
      +  "sales-use-tax-rates",
      +  "sic-codes",
      +  "state-standard",
      +  "stock-analysis",
      +  "tech-stack",
      +  "translate",
      +  "university-info",
      +  "x-handle"
      +]
  2. Changed1 schema field changed
    • removedInput schema / properties / function / enum
      Removed value: -[
      -  "address-parse",
      -  "building-profile",
      -  "business-info",
      -  "business-info-domain",
      -  "business-info-name",
      -  "buying-signals",
      -  "city-standard",
      -  "company-verification",
      -  "competitor-analysis",
      -  "country-standard",
      -  "custom",
      -  "customs-duty-rates",
      -  "email-domain-type",
      -  "email-trust-score",
      -  "entity-type",
      -  "esg-profile",
      -  "eu-vat-rates",
      -  "executive-profile",
      -  "facilities-profile",
      -  "gender-from-name",
      -  "gov-contracts",
      -  "industry-codes",
      -  "ip-profile",
      -  "irs-per-diem-rates",
      -  "muni-issuer-profile",
      -  "name-origin",
      -  "org-standard",
      -  "parent-company",
      -  "phone-profile",
      -  "private-company-deal-intel",
      -  "property-history",
      -  "sales-use-tax-rates",
      -  "sic-codes",
      -  "state-standard",
      -  "stock-analysis",
      -  "tech-stack",
      -  "translate",
      -  "university-info",
      -  "x-handle"
      -]
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description layers on genuinely new behavior: x402 payment-required responses stating exact totals, per-record cost multiplication, pass-through of unrelated fields, automatic input-field matching, and an optional language parameter for premium functions. This is substantial context beyond structured fields.

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 core batching/cost/field-mapping guidance is front-loaded and tight, but the trailing enumeration of all 39 functions with per-record prices is long and largely duplicates what interzoid_enrich_functions is explicitly named to provide. It is useful cost data, yet it inflates the description well beyond what selection requires.

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 an 8-parameter, nested-object tool with no output schema, the description covers record shape and return behavior ('get every record back with the chosen function's output fields appended'), parameter roles, language scope, and cost/payment handling. Nothing an agent needs to call this correctly is missing.

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 the baseline is 3, but the description adds real semantics: the auto-detection rule for lookup_field ('Fields named after the function's inputs, usually "lookup", are used automatically; otherwise set lookup_field'), the pass-through behavior of other fields, and the up-to-12 cap on output_fields for custom.

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 ('Enrich up to 100 records in one call') and explicitly contrasts with the single-record path ('Use this instead of calling a single-record tool once per record'). An agent can distinguish it from siblings like interzoid_business_info without reading schemas.

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 explicit when-to-use routing (batch over single-record), points to interzoid_enrich_functions to inspect inputs/outputs/prices, and adds a clear when-to-pause rule ('Check with the user before running premium functions on many records'). Alternatives and cost conditions are named, not 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.