list_companiesList the authenticated tenant's client companies (name, email, VAT/tax id, country). Useful to resolve a company id before other lookups.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | Client companies, sorted by name. | |
| total | Yes | Number of companies returned. |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "items": {
+ "description": "Client companies, sorted by name.",
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "client_profile": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Client classification: pm (legal entity), pp_pro (sole trader) or consumer."
+ },
+ "country": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "ISO 3166-1 alpha-2 country code."
+ },
+ "email": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Billing email."
+ },
+ "id": {
+ "description": "Company UUID.",
+ "type": "string"
+ },
+ "name": {
+ "description": "Display name.",
+ "type": "string"
+ },
+ "siren": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "French SIREN (9 digits)."
+ },
+ "tax_id": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "VAT number."
+ }
+ },
+ "required": [
+ "id",
+ "name",
+ "email",
+ "tax_id",
+ "siren",
+ "country",
+ "client_profile"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "total": {
+ "description": "Number of companies returned.",
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "items",
+ "total"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotation readOnlyHint=true already establishes that this is a read-only operation. The description adds context about the scope ('authenticated tenant's client companies'), which is useful. No side effects or auth details are needed beyond what the annotation provides.
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?
The description is extremely concise and well-structured. Two sentences cover purpose and usage without any unnecessary words or repetition.
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?
The description is complete for an agent to understand when and why to call this tool. It includes the output fields and the practical use case. Since an output schema exists, return value details are not required in the description.
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?
There are no parameters, so the baseline is 4. The description does not need to elaborate on parameters, and the mention of the output fields (name, email, VAT/tax id, country) indirectly clarifies what the list will contain, which is sufficient.
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 clearly states the action ('List'), the resource ('client companies'), and includes the relevant fields. It also distinguishes itself from sibling tools like get_company by indicating its purpose of resolving a company ID before other lookups.
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 provides a specific use case ('resolve a company id before other lookups'), which gives clear guidance on when to use it. It does not explicitly mention alternatives, but the primary context is well-communicated.
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.