Skip to main content
Glama

eyeot ERP

by io.github.Termi24

eyeot_help

Read-onlyIdempotent

Catalog des actions disponibles sur eyeot ERP. Sans argument : liste les modules et compteur d'actions. Avec module='rh' : liste toutes les actions RH (employes, conges, paie, formations…). Avec action='rh.employes.create' : retourne le détail (path, méthode, params, schema body). Avec search='facture' : recherche les actions matchant. Toujours appeler eyeot_help AVANT eyeot_call pour découvrir l'action exacte.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoAction exacte au format `<module>.<resource>.<verb>` (ex: 'rh.employes.create'). Retourne le schéma complet.
moduleNoNom du module (ex: 'rh', 'finance', 'clients'). Optionnel.
searchNoRecherche textuelle dans les noms d'action et descriptions. Optionnel.

TDQS

A4.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate readOnly, idempotent, non-destructive. The description adds value by specifying output details per parameter (e.g., 'retourne le détail (path, méthode, params, schema body)'), but does not contradict annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured: front-loaded with purpose, then each usage case in separate sentences. No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a catalog tool with 3 optional params and no output schema, the description fully explains the return values for each invocation mode, covering all necessary context for an agent to use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions. The description enriches semantics with examples and format clarifications (e.g., action='rh.employes.create') and explains the output for each param combination.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Catalog des actions disponibles sur eyeot ERP'. It details specific behaviors for different argument combinations (no args, module, action, search), making it distinct from siblings like eyeot_call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs to call eyeot_help before eyeot_call ('Toujours appeler eyeot_help AVANT eyeot_call') and explains when to use each parameter (module, action, search) with examples.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All eyeot ERP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

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.

Resources