Skip to main content
Glama

contact.profile.correct

contact_profile_correct

[需要登录] 纠正联系人健康画像中的错误记录。只删除时 contactid 指定源联系人,本人不传;迁移时额外传 targetContactid。entries.path 指定模块或子字段,entries.match 指定必须唯一命中的字段。匹配不到或多条命中都会失败,不修改数据。

鉴权:需要用户登录令牌,或已经绑定用户的云市场实例凭证。未登录调用返回 401;云市场实例未绑定用户时返回 code=40003 和 data.bindUrl。

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

Input Schema

NameRequiredDescriptionDefault
entriesYes
contactIdNo
contactidNo
targetContactIdNo
targetContactidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses auth requirements (login token or bound cloud-marketplace credential), error outcomes (401, code=40003 with data.bindUrl), and that a no-match or multi-match aborts without modifying data. It does not state whether entries are physically removed or how destructive the delete mode is.

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?

The login-required tag and purpose are front-loaded, followed by mode rules and then auth details. It is dense but mostly earning its place; the auth requirement is effectively restated at the top and in the second paragraph, a minor redundancy.

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

Completeness4/5

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

For a mutation tool with 5 undocumented parameters, no annotations, and no output schema, the definition covers modes, matching semantics, failure behavior, auth, and error codes — enough to call it correctly in most cases. The unresolved camelCase/lowercase parameter duplication is the main remaining ambiguity.

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

Parameters4/5

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

Schema coverage is 0%, yet the description explains contactid (source contact, omit for self), targetContactid (migration only), entries.path (module/subfield), and entries.match (fields that must match uniquely). It leaves the duplicated camelCase params (contactId, targetContactId) and the shape of entries items unexplained, so it compensates substantially but not completely.

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+resource: correct erroneous records in a contact health profile ('纠正联系人健康画像中的错误记录'), which is clearly distinct from plain update/save siblings. It never names a sibling explicitly, so an agent must infer the boundary with contact_update or contact_profile_save, but the purpose itself 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 Guidelines3/5

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

It gives clear mode-level guidance: for delete-only, pass contactid (source contact) and omit the target; for migration, additionally pass targetContactid. However, it offers no guidance on when to pick this tool over contact_update / contact_profile_save, which is the core of tool-selection.

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.

Resources