Skip to main content
Glama
metanmai

libredesk-mcp

by metanmai

update_contact

Update a contact's information including name, email, phone, avatar, and status. Specify the contact ID and any fields to modify.

Instructions

Update Contact PUT /api/v1/contacts/{id} Tags: Contacts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes(path parameter)
first_nameNo(body) Contact's first name
last_nameNo(body) Contact's last name
emailNo(body) Contact's email address
phone_numberNo(body) Contact's phone number
phone_number_country_codeNo(body) ISO country code
filesNo(body, file) New avatar image file to upload — pass an absolute local file path; the server will upload its contents.
avatar_urlNo(body) URL of the contact's avatar image. Pass a valid image URL to update, pass null to remove the avatar, or pass the existing value to keep it unchanged.
enabledNo(body) Whether the contact is enabled
Behavior2/5

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

With no annotations, the description carries the full burden. It only states 'Update' and the endpoint, missing critical traits like whether the update is partial or full, the behavior of optional fields (e.g., null avatar removes it), or any prerequisites (e.g., contact must exist).

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?

The description is very brief, which is concise, but it lacks substantive content. It does not front-load important behavioral information, making it barely adequate.

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 tool with 9 parameters, no output schema, and no annotations, the description should explain update behavior, response format, and side effects. The minimal description leaves the agent without enough context to use the tool correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the parameters are fully documented in the schema. The description adds no additional meaning beyond what the schema already provides, earning the baseline score.

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 clearly states 'Update Contact' and provides the HTTP method and path, making the verb and resource unambiguous. However, it does not differentiate from sibling tools like block_contact, which also modifies a contact.

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 usage guidance is provided. There is no mention of when to use this tool versus alternatives such as block_contact or create_contact. Context signals like required/optional fields or partial vs full update are absent.

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/metanmai/libredesk-mcp'

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