create_client
Créer un client
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | Request body |
eyeot ERP
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description does not add any behavioral context beyond what annotations provide. Annotations show readOnlyHint=false and destructiveHint=false, so it's a write operation. The description should clarify what happens on creation (e.g., duplicate handling, required fields) but fails to do so.
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?
The description is extremely concise (2 words). While it lacks detail, it is not verbose. A slightly longer description would improve clarity, but for a simple purpose, it is not overly wasteful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of the input schema (many optional fields) and no output schema, the description should explain the creation behavior, validation rules, or success criteria. It does none of these, leaving the agent underinformed for a nontrivial operation.
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 coverage is 100% with clear property definitions (types, patterns, enums). The description adds no additional meaning to the parameters, but the schema itself is comprehensive. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description is 'Créer un client' which clearly states the action (create) and resource (client). The name itself also conveys this, so it is clear but does not differentiate from siblings like 'update_client' or 'get_client', which are distinct by their verb.
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, when not to use it, or any contextual cues that help the agent decide between creating a client and other similar actions like creating an opportunity or employee.
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.