Get Company
company_get_companyGetCompany retrieves a single company by ID or code
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | UUID value wrapper. | |
| code | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| company | No |
company_get_companyGetCompany retrieves a single company by ID or code
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | UUID value wrapper. | |
| code | No |
| Name | Required | Description | Default |
|---|---|---|---|
| company | No |
Changes observed during successful MCP inspections.
Output schema / properties / company / anyOfAdded value: +[
+ {
+ "properties": {
+ "address": {
+ "anyOf": [
+ {
+ "properties": {
+ "city": {
+ "type": "string"
+ },
+ "country": {
+ "type": "string"
+ },
+ "county": {
+ "type": "string"
+ },
+ "state": {
+ "type": "string"
+ },
+ "street1": {
+ "type": "string"
+ },
+ "street2": {
+ "type": "string"
+ },
+ "zipCode": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "aliases": {
+ "items": {
+ "description": "Human-readable name (1-255 Unicode chars).",
+ "properties": {
+ "value": {
+ "maxLength": 255,
+ "minLength": 1,
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "code": {
+ "type": "string"
+ },
+ "createdAt": {
+ "anyOf": [
+ {
+ "format": "date-time",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "ein": {
+ "type": "string"
+ },
+ "formedOn": {
+ "type": "string"
+ },
+ "id": {
+ "anyOf": [
+ {
+ "description": "UUID value wrapper.",
+ "properties": {
+ "value": {
+ "format": "uuid",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "logoUrl": {
+ "type": "string"
+ },
+ "name": {
+ "anyOf": [
+ {
+ "description": "Human-readable name (1-255 Unicode chars).",
+ "properties": {
+ "value": {
+ "maxLength": 255,
+ "minLength": 1,
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "source": {
+ "enum": [
+ "COMPANY_SOURCE_UNSPECIFIED",
+ "COMPANY_SOURCE_LOVIE_FORMATION",
+ "COMPANY_SOURCE_USER_CREATED",
+ "COMPANY_SOURCE_IMPORTED"
+ ],
+ "type": "string"
+ },
+ "stateOfFormation": {
+ "type": "string"
+ },
+ "status": {
+ "enum": [
+ "COMPANY_STATUS_UNSPECIFIED",
+ "COMPANY_STATUS_ACTIVE",
+ "COMPANY_STATUS_INACTIVE",
+ "COMPANY_STATUS_SUSPENDED"
+ ],
+ "type": "string"
+ },
+ "type": {
+ "enum": [
+ "COMPANY_TYPE_UNSPECIFIED",
+ "COMPANY_TYPE_LLC",
+ "COMPANY_TYPE_C_CORP",
+ "COMPANY_TYPE_S_CORP",
+ "COMPANY_TYPE_NONPROFIT",
+ "COMPANY_TYPE_SOLE_PROP",
+ "COMPANY_TYPE_PARTNERSHIP"
+ ],
+ "type": "string"
+ },
+ "updatedAt": {
+ "anyOf": [
+ {
+ "format": "date-time",
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "userId": {
+ "anyOf": [
+ {
+ "description": "UUID value wrapper.",
+ "properties": {
+ "value": {
+ "format": "uuid",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "name",
+ "userId"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+]Output schema / properties / company / propertiesRemoved value: -{
- "code": {
- "type": "string"
- },
- "createdAt": {
- "format": "date-time",
- "type": "string"
- },
- "id": {
- "description": "UUID value wrapper.",
- "properties": {
- "value": {
- "format": "uuid",
- "type": "string"
- }
- },
- "type": "object"
- },
- "logoUrl": {
- "type": "string"
- },
- "name": {
- "description": "Human-readable name (1-255 Unicode chars).",
- "properties": {
- "value": {
- "maxLength": 255,
- "minLength": 1,
- "type": "string"
- }
- },
- "type": "object"
- },
- "status": {
- "enum": [
- "COMPANY_STATUS_UNSPECIFIED",
- "COMPANY_STATUS_ACTIVE",
- "COMPANY_STATUS_INACTIVE",
- "COMPANY_STATUS_SUSPENDED"
- ],
- "type": "string"
- },
- "type": {
- "enum": [
- "COMPANY_TYPE_UNSPECIFIED",
- "COMPANY_TYPE_LLC",
- "COMPANY_TYPE_C_CORP",
- "COMPANY_TYPE_S_CORP",
- "COMPANY_TYPE_NONPROFIT",
- "COMPANY_TYPE_SOLE_PROP",
- "COMPANY_TYPE_PARTNERSHIP"
- ],
- "type": "string"
- },
- "updatedAt": {
- "format": "date-time",
- "type": "string"
- },
- "userId": {
- "description": "UUID value wrapper.",
- "properties": {
- "value": {
- "format": "uuid",
- "type": "string"
- }
- },
- "type": "object"
- }
-}Output schema / properties / company / requiredRemoved value: -[
- "name",
- "userId"
-]Output schema / properties / company / typeRemoved value: -"object"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe read-only profile is covered. The description adds the fact that lookup is by ID or code, but it does not disclose behavior such as whether both parameters are allowed, which takes precedence, or what happens when neither is provided. With annotations present this is adequate but not rich.
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?
A single, tightly worded sentence conveys the core purpose and the two lookup methods without extra noise. It is appropriately front-loaded and contains no filler.
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?
With an output schema present, annotations covering safety, and only two simple lookup parameters, the description covers most of what an agent needs. The only notable gap is unstated behavior when both or neither parameter is provided, but this is a minor ambiguity for a straightforward get-by-identifier 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?
Schema coverage is 50%: the 'id' parameter is described as a 'UUID value wrapper' and 'code' has no description. The description helps by indicating that ID and code are alternative lookup keys, which adds meaning beyond the raw schema. However, it does not explain format expectations for 'code' or clarify that exactly one of the two should be supplied.
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?
The description states a precise verb ('retrieves'), a specific resource ('a single company'), and the exact lookup keys ('by ID or code'). This clearly distinguishes the tool from list-oriented siblings like company_get_list_companies and company_get_my_companies, and from the mutation company_update_company.
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?
The description implies use when a caller has a company ID or code and needs one entity, but it does not explicitly state when to prefer this over alternatives or mention any exclusion criteria. There is no guidance about company_get_my_companies or list variants, so the agent must infer the appropriate context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.