Skip to main content
Glama
openprovider

Openprovider MCP Server

Official
by openprovider

update_contact

Update an existing contact's details such as address, name, phone, and other fields using the contact ID.

Instructions

Update an existing contact

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesContact ID to update
additional_dataNoAdditional contact data
addressNoContact address
api_access_enabledNoEnable API access for this contact
commentsNoComments about the contact
company_nameNoCompany name
emailNoContact email address
innNoINN (Individual Taxpayer Number)
is_activeNoWhether the contact is active
kppNoKPP (Tax Registration Reason Code)
localeNoContact locale
nameNoContact name information
passwordNoContact password
phoneNoContact phone information
roleNoContact role (admin, tech, billing, owner)
typeNoContact type
genderNoGender (M/F)
usernameNoUsername for the contact
vatNoVAT number
Behavior2/5

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

The description only says 'Update', implying mutation, but fails to disclose behavioral traits like partial update behavior, idempotency, or required permissions. No annotations are provided to compensate.

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 concise (6 words), but it lacks structure and does not front-load key information. It could benefit from more detail without sacrificing brevity.

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?

Given the tool's complexity (19 parameters, nested objects, no output schema), the description is insufficient. It does not explain return values, error handling, or field relationships.

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 parameters are already well-documented. The tool description adds no additional meaning beyond the schema, resulting in a baseline score of 3.

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 'Update an existing contact' clearly states the action (update) and resource (contact). It is specific but does not differentiate from sibling tools like create_contact or delete_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 guidance on when to use this tool versus alternatives such as create_contact or delete_contact. No prerequisites or exclusions are mentioned.

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/openprovider/openprovider-mcp'

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