Skip to main content
Glama
openprovider

Openprovider MCP Server

Official
by openprovider

create_contact

Add a new contact to your Openprovider account by providing required address, phone, and name details. Contacts are used for domain registration and management.

Instructions

Create a new contact

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
additional_dataNoAdditional contact data
addressYesContact 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
nameYesContact name information
passwordNoContact password
phoneYesContact 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?

No annotations are provided, and the description does not disclose behavioral traits such as side effects, authentication requirements, or data validation. The description 'Create a new contact' offers no behavioral context.

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

Conciseness2/5

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

The description is a single sentence that merely restates the tool name. While concise, it is under-specified and does not add unique value beyond the name.

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

Completeness1/5

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

Given the complexity of 18 parameters, nested objects, and required fields, the description is completely inadequate. It provides no context about contact creation, data constraints, or return values.

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 baseline is 3. The tool description adds no additional meaning beyond the schema, but the schema itself is descriptive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a new contact' is clear but does not differentiate from sibling tools like update_contact or delete_contact. It is a slight improvement over a tautology by adding 'new' but lacks distinguishing details.

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 is provided on when to use this tool versus siblings, such as whether to use it for a new contact or update_contact for an existing one.

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