Skip to main content
Glama
RosenAdvertising

lawruler-mcp

create_lead_full

Creates a new lead intake with full field set including address, date of birth, and contact preferences.

Instructions

Create a new lead/intake with full field set including address, DOB, and contact preferences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
first_nameNo
last_nameNo
full_nameNo
cell_phoneNo
emailNo
email2No
case_typeNo
lead_providerNo
statusNo
summaryNo
address1No
address2No
cityNo
stateNo
zip_codeNo
countyNo
home_phoneNo
business_phoneNo
business_nameNo
dobNo
lead_assigneeNo
lead_ownerNo
hearNo
tagsNo
contact_preferenceNo
when_to_contactNo
case_roleNo
contact_typeNo
campaign_nameNo
languageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations exist, so the description carries full burden. It mentions creation but omits behavioral details like side effects, authentication requirements, idempotency, or return value. Minimal information beyond the name.

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

Conciseness3/5

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

Single sentence, no redundancy, but too short relative to tool complexity. Could be structured to provide more value without adding fluff.

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

Completeness2/5

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

Despite having an output schema (unknown details), the description is insufficient for a tool with 30 parameters and no annotations. It does not cover parameter constraints, defaults, or relation to sibling tools. Completeness is poor.

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 coverage is 0%, so description must compensate. It only lists categories (address, DOB, contact preferences) without explaining individual parameter meaning, format, or constraints. For 30 parameters, this is severely lacking.

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 'Create' and resource 'lead/intake' with specific fields (address, DOB, contact preferences), distinguishing it from simpler siblings like 'create_lead' and 'create_lead_obo'.

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?

No guidance on when to use this tool vs alternatives (e.g., when to use create_lead_full instead of create_lead or update_lead_fields). No exclusion criteria or context provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RosenAdvertising/lawruler-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server