Skip to main content
Glama

HonestCRM

Create a company

create_company

Create a company in the workspace.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCompany name.
customNoCustom field values as an object of custom field id to value.
domainNoWebsite, such as example.com. The scheme and www are removed.
phonesNoPhone numbers. The first one is the primary number.
tagIdsNoIds of tags to attach (at most 20).
addressNoPostal address as free text.
descriptionNoWhat the company does, or notes about it.
ownerUserIdNoThe id of the user who owns the company. Default: the signed-in user.
leadSourceIdNoThe id of the lead source.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already state readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the mutation and safety profile is covered by structured data. The description adds nothing beyond that — notably it does not warn that repeated calls will create duplicate companies (given idempotentHint=false), nor does it describe what is returned or how defaults are applied.

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?

A single short sentence with no wasted words, and the core operation is front-loaded. Its brevity borders on under-specification rather than verbosity, which is penalized under contextual completeness.

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 nine-parameter mutation with a nested free-form custom-field object and no output schema, the description says nothing about return values, duplicate handling, or how custom field ids are validated. The heavy lifting is done by the schema, but an agent gets no behavioral framing before calling a write operation.

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%, and the nine properties are individually documented in the schema, including the default owner and the phone ordering convention. The description adds no meaning beyond the schema, so the baseline of 3 applies.

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 sentence names a specific verb and resource ("Create a company") and adds a scope hint ("in the workspace"), so an agent knows the operation. However, it is essentially a restatement of the tool name and title with no further differentiation from the many other create_* siblings in the catalog.

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?

There is no guidance on when to use this tool versus create_contact, create_deal, or update_company, and no mention of prerequisites such as an existing workspace or required permissions. The agent must infer usage entirely from the name.

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