Skip to main content
Glama
Sign In
Marketic

Marketic

by Das-rebel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

crm_create_lead

Create a CRM lead from marketing data, capturing email, name, company, source, and tags to score and route prospects.

Instructions

Create a new CRM lead from marketing data. Stores lead with email, name, company, source, and scoring data.

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": {
      "email": "<email>"
    },
    "name": "crm_create_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
emailYes
phoneNo
sourceNoorganic
companyNo
job_titleNo
last_nameNo
first_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states creation and stored fields, but does not mention duplicate handling, required permissions, idempotency, or what happens to existing leads. The mention of 'scoring data' is vague and unexplained.

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?

A single, direct sentence that front-loads the action ('Create a new CRM lead') and lists key fields. No wasted words; appropriately concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter tool with no annotations and no output schema, the description is severely incomplete. It does not explain the required email field, default values, the enum for source, or any behavioral nuances. An agent would lack critical information to correctly invoke the tool.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions email, name, company, source, and 'scoring data', but omits phone, tags, and job_title. 'Name' is ambiguous (could refer to first_name/last_name), and 'scoring data' does not correspond to any field in the schema, potentially misleading the agent.

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?

States a clear verb and resource ('Create a new CRM lead') and lists key stored fields (email, name, company, source, scoring data). The purpose is unambiguous, though it does not explicitly differentiate from siblings like crm_create_deal.

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

Usage Guidelines2/5

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

Provides no guidance on when to use this tool versus alternatives. No exclusions, prerequisites, or context such as 'use when you have marketing data' are given.

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

Deploy Server

Other Tools