Versium REACH

Firmographic Append Mcp Tool

firmographic_append

Read-onlyIdempotent

Get business information including company details, location, industry classifications, employee counts, and revenue data.

**Tips for Best Results:**
- Provide domain for fastest, most accurate results
- For business name searches, include complete address information or phone number
- Use `rcfg_require_value` to filter for specific industries or business characteristics

Input Schema

TableJSON Schema

Name	Required	Description
`zip`	No	A 5 digit zip code
`city`	No	A city name
`email`	No	A valid business email address
`phone`	No	A valid 10 digit business phone number
`state`	No	A US state two letter abbreviation
`domain`	No	A business domain
`address`	No	An address (street address line 1)
`business`	No	A business name
`rcfg_max_time`	No	Maximum allowed API run time (in seconds)
`rcfg_require_value`	No	Field/value requirements in "Field=Value" format. Example: ["Industry=Technology"].

Output Schema

TableJSON Schema

Name	Required	Description
`results`	No	Records returned by the Operations API. Record fields pass through unchanged.
`query_id`	No
`warnings`	No
`input_query`	No
`num_matches`	No	Number of matching queries.
`num_results`	No	Number of records returned.
`match_counts`	No	Sparse match counts. An absent key means zero.

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds minimal behavioral detail beyond that, such as performance hints, but does not discuss edge cases, errors, or side effects. It is consistent with the annotations, so no contradiction, but transparency is adequate rather than enhanced.

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

Conciseness5/5

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

The description is brief and well-organized: a one-sentence summary followed by three clear, actionable tips. No redundant or vague language is present, making it easy to parse and apply.

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?

The description gives a clear purpose and practical usage tips, and with an output schema present, it need not elaborate on return values. It could mention what happens when no data is found or how to handle multiple inputs, but for a straightforward append operation, the provided context is sufficient.

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?

The schema already describes each parameter, so coverage is 100%. The description adds extra semantic value by explaining parameter interplay and best practices, such as how 'domain' improves speed and how 'business' searches benefit from address or phone. It does not explain all parameters, but the tips meaningfully enhance the schema descriptions.

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?

The description clearly states the tool's function: 'Get business information including company details, location, industry classifications, employee counts, and revenue data.' This is specific to firmographic data and distinguishes it from sibling tools like contact_append or demographic_append.

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?

The tips provide concrete guidance on how to optimize usage (e.g., 'Provide domain for fastest, most accurate results') and when to include additional parameters (e.g., 'include complete address information or phone number' for business name searches). While it doesn't explicitly contrast with alternative tools, the focus on firmographic data and the naming make the appropriate use case clear.

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

All Versium REACH tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool targets a distinct resource and action: list generation (B2B vs B2C), enrichment (contact, demographic, firmographic, C2B, IP-to-domain), project/list management, job lifecycle, and validation. No two tools appear to do the same thing, so an agent can reliably select the correct one.

Naming Consistency5/5

All tool names follow the verb_noun pattern consistently, using verbs like list, show, create, preview, search, validate, append, and estimate. Even the segmented append tools (c2b_append, contact_append, demographic_append, firmographic_append, ip_to_domain_append) follow the same pattern with clear noun modifiers. No mixed conventions or vague verbs.

Tool Count4/5

With 19 tools, this is on the higher side but still well-scoped for a data enrichment and list-building platform. The count covers distinct functional areas (audience estimation, enrichment, job/project management, list inspection, documentation) without unnecessary bloat. It feels slightly heavy but each tool earns its place.

Completeness4/5

The tool surface covers the core workflows: estimating audiences, creating and monitoring jobs, managing projects and lists, and enriching records with various data types. Minor gaps exist, such as no explicit delete/update operations for projects or lists, and no direct file download for list contents (though preview_list and show_list provide partial coverage). These are non-blocking gaps that agents can work around.

Resources

Need Help?