Skip to main content
Glama

Italian B2B Lead List Scoring, Ranking & JSON Decisions

Get a synthetic MachineSignal output example

get_synthetic_example
Read-onlyIdempotent

Preview the JSON produced when MachineSignal scores, classifies, ranks and prioritizes an Italian B2B lead list. Uses approved synthetic data only and creates no 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": {
      "product_code": "<product_code>"
    },
    "name": "get_synthetic_example"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_codeYesProduct whose approved synthetic output preview should be returned.

Output Schema

NameRequiredDescriptionDefault
exampleYesApproved synthetic product preview; never real buyer or company data.
boundariesYesPermanent safety boundaries of the public MCP discovery server.
canonical_example_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / product_code / description
      Added value: +"Product whose approved synthetic output preview should be returned."
    • 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"
      +    },
      +    "canonical_example_url": {
      +      "format": "uri",
      +      "type": "string"
      +    },
      +    "example": {
      +      "additionalProperties": {},
      +      "description": "Approved synthetic product preview; never real buyer or company data.",
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "example",
      +    "canonical_example_url",
      +    "boundaries"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description discloses data provenance ('approved synthetic data only'), the absence of business side effects ('creates no order'), and the exact persistence behavior ('update only anonymous aggregate counters in memory; submitted data is not saved'). Those are precisely the facts an agent needs before calling a scoring-adjacent endpoint, and they are not derivable from the annotation set.

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 short sentences, no filler, and the payoff (what is returned) leads before the safety and data-handling caveats. Every sentence carries information an agent would otherwise have to guess.

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?

An output schema exists, so the description need not explain return values, and the side-effect and data-provenance story is fully covered. The only small gap is whether the preview differs materially between the two product codes or how large the payload is, but nothing required to call the tool correctly 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 coverage is 100% and the sole parameter carries its own description plus a two-value enum, so the schema already does the work. The description frames the context as an 'Italian B2B lead list' but adds no per-code meaning (for example how MS-DEC-250 differs from MS-ACT-25), which matches the baseline 3 for fully documented schemas.

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 gives a specific verb ('Preview') and a specific resource ('the JSON produced when MachineSignal scores, classifies, ranks and prioritizes an Italian B2B lead list'), so the agent knows this returns a sample output rather than live scoring. The clause 'creates no order' separates it from siblings such as prepare_order_intent, and the preview framing separates it from get_product_catalog or get_purchase_requirements.

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 makes the use case clear: inspect the shape of MachineSignal output using approved synthetic data, before (or without) committing to an order. It supplies an implicit condition for choosing this tool ('creates no order'), but it does not explicitly name an alternative tool or state when not to use it, so it falls short of a full 5.

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