Skip to main content
Glama

accelo_create_address

Create a new address for a company or contact in Accelo CRM, including street, city, state, country, and postal details.

Instructions

Create a new address.

Args: against_type: Object type (required) — 'company' or 'contact' against_id: Object ID (required) title: Name for the address, e.g. "Head Office" street1: First line of street address street2: Second line of street address city: City name state: State/province name (use if state_id unknown) state_id: State ID (preferred over state name) country: Country name (use if country_id unknown) country_id: Country ID (preferred over country name) zipcode: Postcode/zipcode postal: "yes" or "no" — is this a postal address? physical: "yes" or "no" — is this a physical address? fields: Additional fields to return

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNo
stateNo
titleNo
fieldsNo
postalNo
countryNo
street1No
street2No
zipcodeNo
physicalNo
state_idNo
against_idYes
country_idNo
against_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description bears full burden. It does not disclose side effects, required permissions, whether the address is immediately available, or error conditions. Only states it creates an address, with no behavioral depth.

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?

The description is well-structured with a header and bullet-like param list. It's front-loaded with the core action 'Create a new address.' and then details. Not overly verbose, but could be slightly more concise by omitting redundant labels like 'Street1: First line of street address' given the name is self-explanatory.

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

Completeness3/5

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

For a 14-parameter mutation tool with no annotations and no output schema, the description provides necessary parameter info but lacks behavioral context, such as return values, error handling, or permissions. It's minimally adequate but leaves gaps an agent might need.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It does so by listing all 14 parameters with brief explanations (e.g., 'state: State/province name (use if state_id unknown)'), clarifying required vs optional and mutual exclusivity between name and ID fields. This is strong compensation, though some parameters like 'fields' are vaguely explained ('Additional fields to return').

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 the specific verb and resource: 'Create a new address.' This directly distinguishes it from siblings like accelo_update_address and accelo_list_addresses. Missing explicit sibling differentiation, but the purpose is unambiguous.

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 or in what context. It doesn't mention prerequisites (e.g., needing an existing company or contact) or exclusions. The agent must infer usage entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools