Add a new contact to your Offorte contact database. Specify whether it's an organization or a person and include details like name, email, phone, and address.
Create a new contact (organisation or person/individual)
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | ||
| name | Yes | ||
| tags | No | ||
| type | Yes | ||
| No | |||
| phone | No | ||
| state | No | ||
| mobile | No | ||
| street | No | ||
| country | No | ||
| No | |||
| zipcode | No | ||
| No | |||
| internet | No | ||
| lastname | No | ||
| No | |||
| firstname | No | ||
| No | |||
| coc_number | No | ||
| salutation | No | ||
| vat_number | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description only says 'Create' with no behavioral details beyond annotations. Annotations provide openWorldHint, but description adds no context about side effects, permissions, or idempotency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence is very concise, but given the tool's complexity (21 parameters), it could benefit from additional structure without being verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, minimal parameter documentation, and no mention of return values or error handling. The description is insufficient for an agent to fully understand how to use the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 21 parameters and 0% schema description coverage, the description does not explain any parameter meaning. It mentions 'organisation or person/individual' which relates to the type parameter, but no other parameter semantics are provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool creates a contact, specifying subtypes (organisation or person/individual), which distinguishes it from sibling search tools. The verb 'create' and resource 'contact' are explicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 like search_contact_organisations or create_proposal. Missing context on prerequisites or post-conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/offorte/offorte-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server