Skip to main content
Glama

Set the company for a Concordium identity

set_concordium_company_details
Idempotent

The regular route, step 1: sets the company the Concordium identity is for. Give leiNumber if the company has an LEI with any issuer (its details are taken from the LEI record), otherwise its business registration details: legalName, countryCode, businessRegistryNumber, addressLine1, city, postalCode and entityCreationDate, and if you know them regionCode, registrationAuthorityCode, legalFormElfCode (lookup_legal_form) and addressLine2. Confirm the details with the user first. Then upload documents with get_concordium_document_upload_link.

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

Input Schema

NameRequiredDescriptionDefault
cityNoRegistered address, city.
idCredPubYesThe idCredPub from start_concordium_company_verification.
legalNameNoThe company's legal name.
leiNumberNoThe company's 20-character LEI, if it has one. Leave out to give registration details instead.
postalCodeNoRegistered address, postal code.
regionCodeNoThe region of registration, ISO 3166-2, e.g. US-DE, where the country has regional registers.
countryCodeNoThe country of registration, ISO 3166-1 alpha-2, e.g. DK.
addressLine1NoRegistered address, first line.
addressLine2NoRegistered address, second line.
legalFormElfCodeNoThe 4-character ELF code of the legal form, from lookup_legal_form, if known.
entityCreationDateNoThe date the company was founded, yyyy-MM-dd.
businessRegistryNumberNoThe company's number in the business register, e.g. its CVR number.
registrationAuthorityCodeNoThe GLEIF registration authority code of the business register, e.g. RA000170, if known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly=false, idempotent=true, non-destructive, openWorld), so the bar is lower. The description still adds real context: it is a mutation that must be user-confirmed before submission, LEI details override manual fields, and how it chains to document upload.

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?

Purpose is front-loaded and every sentence carries routing or parameter-selection information. It is dense and slightly run-on as a single paragraph listing many fields, but there is little waste.

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

Completeness4/5

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

For a 13-parameter mutating workflow tool this is close to complete: it gives the step position, the branch logic, the confirmation requirement, and the next tool. No output schema exists, but for a setter that is acceptable; only the alternative routes are left unnamed.

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 schema already documents every parameter and the baseline is 3. The description adds the conditional grouping (leiNumber vs. the registration set) and flags which fields are optional 'if you know them', but no syntax or format detail beyond the schema.

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

Purpose5/5

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

States a specific verb+resource ('sets the company the Concordium identity is for') and situates itself as 'the regular route, step 1'. It names the follow-up sibling (get_concordium_document_upload_link) and lookup_legal_form, so an agent can place it in the flow without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit branch condition: supply leiNumber if the company has an LEI (details pulled from the LEI record), otherwise the registration fields. It also states a prerequisite ('Confirm the details with the user first') and the next step. It does not, however, name the alternative routes it contrasts 'the regular route' against, so a sibling-exclusion is only implied.

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