billingo_get_productRetrieve a single product by ID from Billingo to access product details for invoicing, pricing, or order workflows.
Returns a single product by id.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Product id. |
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| ean | No | ||
| sku | No | ||
| vat | No | ||
| name | No | ||
| unit | No | ||
| comment | No | ||
| currency | No | ||
| net_unit_price | No | ||
| gross_unit_price | No |
Changes observed during successful MCP inspections.
v0.1.3Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": {},
+ "properties": {
+ "comment": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "currency": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "ean": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "gross_unit_price": {
+ "type": [
+ "number",
+ "string",
+ "null"
+ ]
+ },
+ "id": {
+ "type": "number"
+ },
+ "name": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "net_unit_price": {
+ "type": [
+ "number",
+ "string",
+ "null"
+ ]
+ },
+ "sku": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "unit": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "vat": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "id"
+ ],
+ "type": "object"
+}v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds nothing beyond the bare operation – no error behavior for missing ids, no note about which organization's data is queried despite openWorldHint being true.
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 front-loaded sentence with no filler. It is efficient, though the terseness leaves the reader with nothing beyond the bare statement of the operation.
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?
An output schema exists, so return values need not be described, and annotations cover the safety profile for this simple one-parameter read. The only gap is the lack of any error or not-found guidance, which is minor here.
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 100% and the single id parameter is documented in the schema as "Product id." The description restates the same fact without adding format, range, or source-of-id guidance, so the schema does all the work.
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?
States a specific verb (returns) and resource (a single product) scoped by id, which clearly separates it from a list operation. It does not name a sibling such as billingo_list_products, so differentiation is only implicit in the wording.
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 phrase "single product by id" implies this is the fetch-one counterpart to a list tool, which an agent can infer from the sibling names. There is no explicit when-to-use or when-not-to-use statement, and no mention of what happens if the id is unknown.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.