Skip to main content
Glama

Italian B2B Lead List 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. Calls update only anonymous aggregate counters in memory; submitted data is not saved.

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": {
      "customer_type": "<customer_type>",
      "need_domain": "<need_domain>",
      "need_action": "<need_action>",
      "need_object": "<need_object>",
      "desired_output": "<desired_output>"
    },
    "name": "map_business_need"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoLegacy 1.2.0 compatibility for Italian demand. Omit it when origin_market is supplied.
urgencyNoHow soon the capability would be useful; defaults to exploratory.
recurrenceNoWhether the need is one-off, recurring or continuous; defaults to unknown.
budget_bandNoOptional coarse willingness-to-pay band in EUR; never send payment data.
need_actionYesPrimary action the machine wants the capability to perform.
need_domainYesBroad business domain of the requested capability; use other only when none applies.
need_objectYesBusiness object or subject on which the action should operate.
customer_typeYesOnly business demand is observed; this does not expand commercial eligibility.
origin_marketNoSelf-declared coarse origin bucket used only for aggregate research; defaults to UNKNOWN_NOT_DECLARED. Foreign buckets never enable sales.
desired_outputYesMachine-readable or operational result the buyer wants.
existing_product_fitNoWhether an existing MachineSignal product appears to fit; defaults to unknown.

Output Schema

NameRequiredDescriptionDefault
scopeYes
boundariesYesPermanent safety boundaries of the public MCP discovery server.
signal_typeYes
order_createdYes
origin_marketYes
persists_dataYes
mapping_statusYes
need_signatureYes
product_createdYes
free_text_acceptedYes
buyer_data_acceptedYes
market_verificationYes
existing_product_fitYes
checkout_url_returnedYes
potential_product_gapYes
provider_call_enabledYes
commercial_eligibilityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Commercial scope is limited to Italy."New value: +"Legacy 1.2.0 compatibility for Italian demand. Omit it when origin_market is supplied."
    • changedInput schema / properties / customer_type / description
      Previous value: -"Only business buyers are in scope."New value: +"Only business demand is observed; this does not expand commercial eligibility."
    • addedInput schema / properties / origin_market
      Added value: +{
      +  "description": "Self-declared coarse origin bucket used only for aggregate research; defaults to UNKNOWN_NOT_DECLARED. Foreign buckets never enable sales.",
      +  "enum": [
      +    "IT",
      +    "EU_NON_IT",
      +    "EXTRA_EU",
      +    "UNKNOWN_NOT_DECLARED"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "country",
      -  "customer_type",
      -  "need_domain",
      -  "need_action",
      -  "need_object",
      -  "desired_output"
      -]New value: +[
      +  "customer_type",
      +  "need_domain",
      +  "need_action",
      +  "need_object",
      +  "desired_output"
      +]
    • addedOutput schema / properties / commercial_eligibility
      Added value: +{
      +  "enum": [
      +    "b2b_italy_sales_scope",
      +    "research_only_not_commercially_eligible"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / market_verification
      Added value: +{
      +  "const": "structured_self_declared_bucket_not_identity_verified",
      +  "type": "string"
      +}
    • addedOutput schema / properties / need_signature / properties / origin_market
      Added value: +{
      +  "enum": [
      +    "IT",
      +    "EU_NON_IT",
      +    "EXTRA_EU",
      +    "UNKNOWN_NOT_DECLARED"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / need_signature / required
      Previous value: -[
      -  "domain",
      -  "action",
      -  "object",
      -  "output",
      -  "urgency",
      -  "recurrence",
      -  "budget_band"
      -]New value: +[
      +  "origin_market",
      +  "domain",
      +  "action",
      +  "object",
      +  "output",
      +  "urgency",
      +  "recurrence",
      +  "budget_band"
      +]
    • addedOutput schema / properties / origin_market
      Added value: +{
      +  "enum": [
      +    "IT",
      +    "EU_NON_IT",
      +    "EXTRA_EU",
      +    "UNKNOWN_NOT_DECLARED"
      +  ],
      +  "type": "string"
      +}
    • removedOutput schema / properties / scope / const
      Removed value: -"B2B_Italy_general_business_need"
    • addedOutput schema / properties / scope / enum
      Added value: +[
      +  "B2B_Italy_general_business_need",
      +  "B2B_global_demand_research_sales_italy_only"
      +]
    • changedOutput schema / required
      Previous value: -[
      -  "mapping_status",
      -  "scope",
      -  "need_signature",
      -  "existing_product_fit",
      -  "potential_product_gap",
      -  "signal_type",
      -  "free_text_accepted",
      -  "buyer_data_accepted",
      -  "persists_data",
      -  "product_created",
      -  "order_created",
      -  "checkout_url_returned",
      -  "provider_call_enabled",
      -  "boundaries"
      -]New value: +[
      +  "mapping_status",
      +  "scope",
      +  "origin_market",
      +  "market_verification",
      +  "commercial_eligibility",
      +  "need_signature",
      +  "existing_product_fit",
      +  "potential_product_gap",
      +  "signal_type",
      +  "free_text_accepted",
      +  "buyer_data_accepted",
      +  "persists_data",
      +  "product_created",
      +  "order_created",
      +  "checkout_url_returned",
      +  "provider_call_enabled",
      +  "boundaries"
      +]
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, the description discloses scope constraints, that only closed semantic fields are accepted, that no product or order is created, and that submitted data is not saved. It also clarifies anonymous in-memory aggregate counters, which is useful behavioral context. These details are consistent with the read-only, non-destructive, closed-world profile.

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

Conciseness4/5

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

The description is front-loaded and compact, with no obvious filler. Each sentence adds scope, safety, or data-handling context. It could be marginally tighter, but it is well structured for an agent.

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, full schema coverage, and an output schema, the description supplies the key non-schema context: research-only vs commercial scope, no persistence of submitted data, and no product/order creation. It lacks explicit sibling routing guidance, but is otherwise complete enough for correct invocation.

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 schema already documents all parameters and enum meanings. The description adds only general context that inputs are closed semantic fields, without explaining individual parameters beyond the schema.

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 description states a specific verb and resource: mapping a structured B2B business need for aggregate product research. It also distinguishes Italian commercial scope from foreign research-only signals. It does not explicitly differentiate itself from siblings such as check_buyer_fit or prepare_order_intent, so it stops short of a 5.

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 description gives clear usage context: structured B2B needs, aggregate research, Italy-only commercial sales scope, and foreign signals as research-only. It also states that no product or order is created. It does not name alternatives or explicitly say when another sibling tool should be used instead.

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