Skip to main content
Glama

create_prospect

Manually add a prospect to the pipeline (confirm-gated) — for a lead that came in outside the platform (a call, a walk-in, a referral).

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

Input Schema

NameRequiredDescriptionDefault
goalNo
nameYes
noteNo
emailNo
phoneNo
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the mutation profile is known. The description adds that the operation is 'confirm-gated', which is real behavioral context, but that same fact is spelled out in the schema's confirm parameter, and nothing is said about duplicate handling, side effects, or permissions.

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 front-loaded sentence with the action first and the qualifying examples after. Every clause earns its place: the parenthetical both defines scope and prevents misrouting.

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

Completeness3/5

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

With six parameters, mostly undocumented, and no output schema, the definition leaves the agent guessing about what the preview versus the executed response contains and how optional fields like email or goal affect the created record. It does correctly flag the confirm gate, which is the highest-risk detail.

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 only 17% — just the confirm flag — leaving name, goal, note, email and phone undocumented in structured data. The description mentions none of these fields, so it does not compensate for the coverage gap; it only names the resource being created.

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 specific verb and resource ('Manually add a prospect to the pipeline') plus a scoping qualifier ('a lead that came in outside the platform'). This clearly separates it from the note/assignment/status siblings, though no other create-style tool is named as a contrast.

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?

Gives concrete triggering contexts (a call, a walk-in, a referral) and implicitly excludes platform-sourced leads via 'outside the platform'. It stops short of naming an alternative tool for leads that were captured in-product, so the routing is contextual rather than explicit.

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.