Israel Business Intelligence MCP

Preview Israeli company identity - free and limited

preview_company

Read-onlyIdempotent

FREE LIMITED PREVIEW for an Israeli company legal name or company number. Returns only identity, registry status, match candidates, confidence, and an exact next action. It never returns field-level evidence, source URLs, address, incorporation, annual-report, or law-violation fields. Use the paid verify_company tool for the complete evidence-backed public-registry result.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	No	Optional Israeli city used to disambiguate companies with similar names.
`website`	No	Optional public company website used only as supporting resolution context.
`language`	No	Language for the human-readable summary: en or he. Defaults to en.	en
`company_name`	No	Israeli legal or trading name. Provide this or company_number; add city when the name may be ambiguous.
`company_number`	No	Israeli company registration number. A nine-digit number gives the most reliable exact match.
`expected_entity_type`	No	Optional expected legal entity type, such as private company, used for disambiguation.

Output Schema

TableJSON Schema

Name	Required	Description
`mode`	Yes
`company`	Yes
`candidates`	Yes
`checked_at`	Yes
`confidence`	Yes
`request_id`	Yes	Unique preview request identifier.
`next_action`	Yes
`preview_version`	Yes	Preview contract version.
`full_verification`	Yes
`resolution_status`	Yes
`preview_limitations`	Yes

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds further behavioral detail: it is a preview that returns only certain fields, never field-level evidence, source URLs, address, incorporation, annual-report, or law-violation fields. This gives agents a clear contract of the tool's limitations beyond what annotations convey.

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 four short sentences, immediately front-loading the free preview nature and the input type ('legal name or company number'). Every sentence adds value: scope, returns, exclusions, and alternative tool routing. There is no filler.

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?

Given the rich input schema, output schema, and annotations, the description is fully sufficient for an agent to select and invoke the tool. It states expected inputs, output scope, exclusions, and the paid alternative. No critical operational context is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

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

Schema description coverage is 100%, so the input schema already fully documents all six parameters with rich detail. The description adds only the high-level notion of looking up by legal name or company number, which is already reflected in the parameter descriptions. No significant additional parameter meaning is provided.

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 states a specific verb ('preview') and resource (Israeli company identity) with scope qualifiers ('FREE LIMITED'). It explicitly differentiates from verify_company by listing the exact fields returned and excluded. An agent can immediately understand what this tool does and where it stops.

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?

The description clearly identifies when to use this tool (free limited identity preview) and explicitly directs agents to verify_company for the complete evidence-backed result. It also tells the agent what this tool will not provide, so there is no ambiguity about selecting the wrong sibling.

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

All Israel Business Intelligence MCP 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.4/5.0

Disambiguation5/5

Each tool has a clearly distinct role: describe_service explains capabilities, get_schema provides data formats, preview_company offers a free limited lookup, and verify_company returns paid full evidence. The overlap between preview_company and verify_company is explicitly delineated by scope and pricing, leaving no ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: describe_service, get_schema, preview_company, verify_company. The verbs clearly indicate the action and nouns identify the target, creating a predictable and uniform naming scheme.

Tool Count5/5

With only 4 tools, the server is tightly scoped to its purpose of Israeli company verification. Each tool serves a necessary function—discovery, integration support, free preview, and paid full verification—without unnecessary bloat or missing essentials.

Completeness5/5

The tool set covers the full verification workflow: understand service limits, obtain schemas, perform a free preview, and run a paid full verification. Since the domain is read-only verification, there are no missing lifecycle operations, and the preview-to-verify path has no dead ends.

Resources

Need Help?