create_product
Créer un produit (catalogue stock)
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | Request body |
eyeot ERP
TDQS
C2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does not add behavioral context beyond the name 'create product'. Annotations indicate mutation (readOnlyHint=false) but no other traits like idempotency or error behavior are disclosed. Additional context such as duplicate handling or required permissions would improve transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short (one phrase) but lacks necessary detail. Conciseness is not valuable when it omits critical information; this is under-specification, not efficient communication.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of the nested input schema (17+ fields) and no output schema, the description is completely inadequate. It fails to explain return values, validation rules, or any side effects, leaving an agent poorly equipped to use the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Despite the input schema having many nested properties with no descriptions, the tool description provides no explanation of any parameter. The schema description coverage is effectively low because only the top-level 'body' has a description. The agent is left without guidance on what each field means.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the verb 'Créer' (create) and resource 'produit' (product), which is clear enough. However, it does not differentiate from sibling tools like create_client or create_invoice, and the phrase '(catalogue stock)' is ambiguous.
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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, constraints, or context that would help an agent decide to use this over other create tools.
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.
TDQS
C2.9/5.0
Disambiguation4/5
Most tools target distinct resources and actions (e.g., create_client vs. list_clients). However, generic tools like eyeot_call overlap with many specific tools, and there's potential confusion between convert_opportunity_to_quote, create_quote, and accept_quote, though descriptions help distinguish them.
Naming Consistency3/5
The majority follow verb_noun pattern (create_client, list_invoices), but there are outliers like eyeot_call, eyeot_help, stock_dashboard, dashboard_kpis, whoami, and search. The mix of French and English is consistent but slight inconsistency in structure.
Tool Count4/5
33 tools cover multiple ERP modules (CRM, HR, inventory, sales, IT). While on the higher end, each module has necessary operations. The presence of generic eyeot_call suggests the tool surface could be larger, but the count is still reasonable for the scope.
Completeness2/5
Only clients have update and no deletes exist. Many resources (products, employees, orders, quotes, invoices, opportunities, tickets) lack update/delete operations. This creates dead ends for agents that need to modify or remove data.