Dievio

Update Saved Lead

update_saved_lead

DestructiveIdempotent

Edit stored contact fields or its additional data; cannot change ownership or billing fields.

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": {
      "request_id": "<request_id>",
      "lead_id": "<lead_id>",
      "changes": "<changes>"
    },
    "name": "update_saved_lead"
  }
}

Input Schema

Name	Required	Description
`changes`	Yes
`lead_id`	Yes
`request_id`	Yes	Stable idempotency UUID. Reuse with identical arguments on retry.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already disclose that this is a destructive, idempotent mutation, so the description is not the primary safety signal. The description adds useful scope detail by stating that ownership and billing fields cannot be changed, but it does not explain partial-update behavior, null handling, or how omitted fields are treated.

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?

The description is a single front-loaded sentence with no redundant or wasted phrasing. It delivers the core action and key constraint efficiently.

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?

For a destructive mutation with a nested changes object, only 33% schema description coverage, and no output schema, the description is too thin. It omits partial-update semantics, what happens when fields are omitted, how null values behave, and what the caller should expect after the edit.

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 33%, so the description needs to compensate for undocumented parameters. It refers generically to 'contact fields or its additional data' but never explains the required lead_id or the structure and semantics of the changes object, including that properties are restricted by additionalProperties=false and many fields accept null.

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 states a specific verb ('Edit') and resource ('stored contact fields or its additional data'), making the operation recognizable. It also clarifies an important boundary by excluding ownership and billing fields, though it does not explicitly differentiate the tool from siblings such as delete_saved_leads or update_list.

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

Usage Guidelines3/5

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

Usage is implied through 'Edit stored contact fields', and the description provides a when-not constraint for ownership and billing fields. However, it does not name an alternative tool or explain when to choose this over related operations like delete_saved_leads or update_list.

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

All Dievio tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?