Dunefox Voice MCP Server

Find the lead a call belongs to

get_lead_for_call

Read-only

Retrieve the lead record associated with a specific call UUID. Use it to connect call data to the right contact and follow up accurately.

Instructions

The lead record linked to a given call.

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

Input Schema

Name	Required	Description	Default
`callUuid`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 28, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. Beyond that, the description adds nothing behavioral: it does not say whether the lookup can fail, what happens for a call with no lead, or whether a lead can be linked to multiple calls. It restates the operation rather than disclosing traits.

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

Conciseness4/5

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

A single short sentence with no filler, and the resource-plus-relationship information is front-loaded. It is efficient, though the terseness comes at the cost of the guidance and behavioral detail scored elsewhere.

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?

With no output schema, the description must carry the return-value burden, and it only minimally indicates that a lead record is returned without describing its shape or the no-lead/null case. For a lookup tool keyed on an undocumented identifier, this leaves real gaps.

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% for the single required parameter. The phrase 'a given call' vaguely implies callUuid identifies the call, but the description supplies no format, source, or mismatch behavior to compensate for the missing schema documentation, leaving the only parameter effectively undocumented.

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?

The description names a specific resource (the lead record) and the exact relationship it resolves (the lead linked to a given call), so an agent can distinguish it from get_call, list_leads, or create_lead. It is a noun fragment rather than a verb+resource statement, but the retrieval intent is unambiguous.

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?

There is no when-to-use guidance at all: no statement of prerequisites, no mention of alternatives such as list_leads or get_call, and no indication of what to do when a call has no associated lead. The agent must infer usage entirely from the name.

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