Skip to main content
Glama

Italian B2B Lead List Scoring, Ranking & JSON Decisions

by it.machinesignal
OverviewDiscussionsAdmin

Check MachineSignal buyer fit

check_buyer_fit
Read-onlyIdempotent

Check whether an Italian B2B buyer with an existing company, domain, CRM or lead list can use MS-DEC-250 to score, rank and prioritize up to 250 records. Coarse non-personal facts only; it creates no order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYesTwo-letter country code, for example IT.
primary_needNoOptional non-personal demand category used only in ephemeral aggregate counters; never send free text or buyer data.
customer_typeYesBuyer type. MachineSignal accepts B2B only.
requested_product_codeNoProduct being considered. Defaults to the entry product MS-DEC-250.
has_existing_company_listYesWhether the buyer already has a company, domain, CRM or lead list to evaluate.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonYes
eligibleYes
boundariesYesPermanent safety boundaries of the public MCP discovery server.
fit_statusYes
reason_codeYes
next_resourceNo
ready_to_prepareYes
checkout_url_returnedNo
recommended_next_toolNo
requested_product_codeYes
recommended_next_argumentsNo
next_step_after_preparationNo
buyer_data_must_remain_localYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / primary_need
      Added value: +{
+  "description": "Optional non-personal demand category used only in ephemeral aggregate counters; never send free text or buyer data.",
+  "enum": [
+    "score_existing_company_list",
+    "discover_target_companies",
+    "prioritize_leads",
+    "market_potential_analysis",
+    "deep_company_analysis",
+    "build_actionable_campaign",
+    "crm_workflow_automation",
+    "monitor_market_changes",
+    "competitor_analysis",
+    "other_structured_b2b_need"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / buyer_data_must_remain_local
      Added value: +{
+  "const": true,
+  "type": "boolean"
+}
    • addedOutput schema / properties / next_step_after_preparation
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / ready_to_prepare
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / recommended_next_arguments
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "product_code": {
+      "const": "MS-DEC-250",
+      "type": "string"
+    }
+  },
+  "required": [
+    "product_code"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / recommended_next_tool
      Added value: +{
+  "const": "prepare_order_intent",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "fit_status",
-  "eligible",
-  "requested_product_code",
-  "reason_code",
-  "reason",
-  "boundaries"
-]New value: +[
+  "fit_status",
+  "eligible",
+  "requested_product_code",
+  "reason_code",
+  "reason",
+  "ready_to_prepare",
+  "buyer_data_must_remain_local",
+  "boundaries"
+]
  2. Changed4 schema fields changed
    • addedInput schema / properties / customer_type / description
      Added value: +"Buyer type. MachineSignal accepts B2B only."
    • addedInput schema / properties / has_existing_company_list / description
      Added value: +"Whether the buyer already has a company, domain, CRM or lead list to evaluate."
    • addedInput schema / properties / requested_product_code / description
      Added value: +"Product being considered. Defaults to the entry product MS-DEC-250."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "boundaries": {
+      "additionalProperties": false,
+      "description": "Permanent safety boundaries of the public MCP discovery server.",
+      "properties": {
+        "accepts_buyer_data": {
+          "const": false,
+          "type": "boolean"
+        },
+        "b2b_italy_only": {
+          "const": true,
+          "description": "Only Italian B2B buyers are in commercial scope.",
+          "type": "boolean"
+        },
+        "checkout_url_exposed": {
+          "const": false,
+          "type": "boolean"
+        },
+        "external_outreach_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "invoice_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "marketplace_publication_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "mode": {
+          "const": "public_read_only_discovery",
+          "description": "Public discovery mode; never an order-processing surface.",
+          "type": "string"
+        },
+        "order_tool_exposed": {
+          "const": false,
+          "type": "boolean"
+        },
+        "payment_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "persists_data": {
+          "const": false,
+          "type": "boolean"
+        },
+        "provider_call_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "provider_reference_loaded": {
+          "const": false,
+          "type": "boolean"
+        },
+        "sdi_enabled": {
+          "const": false,
+          "type": "boolean"
+        },
+        "wise_payout_enabled": {
+          "const": false,
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "mode",
+        "b2b_italy_only",
+        "accepts_buyer_data",
+        "persists_data",
+        "order_tool_exposed",
+        "checkout_url_exposed",
+        "provider_reference_loaded",
+        "provider_call_enabled",
+        "payment_enabled",
+        "invoice_enabled",
+        "sdi_enabled",
+        "wise_payout_enabled",
+        "external_outreach_enabled",
+        "marketplace_publication_enabled"
+      ],
+      "type": "object"
+    },
+    "checkout_url_returned": {
+      "const": false,
+      "type": "boolean"
+    },
+    "eligible": {
+      "type": "boolean"
+    },
+    "fit_status": {
+      "enum": [
+        "blocked",
+        "not_fit",
+        "continuation_entitlement_required",
+        "fit_for_controlled_dec_order_intent"
+      ],
+      "type": "string"
+    },
+    "next_resource": {
+      "format": "uri",
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "reason_code": {
+      "type": "string"
+    },
+    "requested_product_code": {
+      "enum": [
+        "MS-DEC-250",
+        "MS-ACT-25"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "fit_status",
+    "eligible",
+    "requested_product_code",
+    "reason_code",
+    "reason",
+    "boundaries"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds 'Coarse non-personal facts only' and the warning in parameter descriptions about not sending free text or buyer data, which enriches the behavioral context. No contradictions found.

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 consists of two efficient sentences: the first captures the primary purpose and conditions, the second adds safety context. No superfluous words; every element earns its place.

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 the tool's moderate complexity (5 parameters, 3 enums, output schema exists but not shown), the description covers the key use case and behavioral constraints. It could be improved by explicitly noting that the country parameter should be 'IT' for Italian buyers, but the schema handles that implicitly.

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% with good parameter descriptions. The tool description further clarifies how parameters interconnect (e.g., 'Italian' implies country='IT', 'B2B' ties to customer_type, 'existing company' ties to has_existing_company_list). This adds meaning beyond the schema alone.

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 verb 'Check' and the specific resource (buyer fit for MS-DEC-250), along with key conditions (Italian, B2B, existing company list). It also implicitly distinguishes from sibling tools like prepare_order_intent by focusing on eligibility rather than order creation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool (checking eligibility before order), but does not explicitly state when not to use it or mention alternatives. The directive 'it creates no order' hints at its safe, non-committal nature, but lacks explicit exclusionary guidance.

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 List Scoring, Ranking & JSON Decisions toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources