Italian B2B Lead Scoring, Ranking & JSON Decisions

Map a general B2B business need for product research

map_business_need

Read-onlyIdempotent

Map any structured B2B business need from Italy or a foreign market for aggregate product research. Italy remains the only commercial sales scope; foreign signals are research-only. The tool accepts only closed semantic fields and never creates a product or order.

Input Schema

TableJSON Schema

Name	Required	Description
`country`	No	Legacy 1.2.0 compatibility for Italian demand. Omit it when origin_market is supplied.
`urgency`	No	How soon the capability would be useful; defaults to exploratory.
`recurrence`	No	Whether the need is one-off, recurring or continuous; defaults to unknown.
`budget_band`	No	Optional coarse willingness-to-pay band in EUR; never send payment data.
`need_action`	Yes	Primary action the machine wants the capability to perform.
`need_domain`	Yes	Broad business domain of the requested capability; use other only when none applies.
`need_object`	Yes	Business object or subject on which the action should operate.
`customer_type`	Yes	Only business demand is observed; this does not expand commercial eligibility.
`origin_market`	No	Self-declared coarse origin bucket used only for aggregate research; defaults to UNKNOWN_NOT_DECLARED. Foreign buckets never enable sales.
`desired_output`	Yes	Machine-readable or operational result the buyer wants.
`existing_product_fit`	No	Whether an existing MachineSignal product appears to fit; defaults to unknown.

Output Schema

TableJSON Schema

Name	Required	Description
`scope`	Yes
`boundaries`	Yes	Permanent safety boundaries of the public MCP discovery server.
`signal_type`	Yes
`order_created`	Yes
`origin_market`	Yes
`persists_data`	Yes
`mapping_status`	Yes
`need_signature`	Yes
`product_created`	Yes
`free_text_accepted`	Yes
`buyer_data_accepted`	Yes
`market_verification`	Yes
`existing_product_fit`	Yes
`checkout_url_returned`	Yes
`potential_product_gap`	Yes
`provider_call_enabled`	Yes
`commercial_eligibility`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedJul 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds key behaviors: never creates a product or order, and clarifies territorial scope for research vs commercial use.

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?

Three concise sentences front-load the core purpose, then add scope constraints. No unnecessary words, each sentence adds value.

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?

Given 11 parameters, an output schema exists, and annotations cover safety, the description adequately adds key constraints (scope, non-creation). Could mention that mapping implies aggregate research only, but overall sufficient.

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 coverage is 100%, so baseline is 3. The description ('accepts only closed semantic fields') adds minimal value beyond the schema's detailed enumerations and 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 maps structured B2B business needs for product research, with specific scopes (Italy or foreign). It distinguishes from siblings like prepare_order_intent by noting it never creates a product or order.

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?

Provides clear context on when to use (mapping needs for research) and when not (never creates products/orders), and limits commercial scope to Italy. Lacks explicit references to sibling tools but context is sufficient.

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

All Italian B2B Lead Scoring, Ranking & JSON Decisions 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.

Resources

Need Help?