Skip to main content
Glama

eyeot ERP

by io.github.Termi24

eyeot_call

Destructive

Exécute une action eyeot ERP par son nom canonique. Format action : <module>.<resource>.<verb> (ex: 'clients.list', 'rh.employes.create', 'quotes.send'). Toujours utiliser eyeot_help d'abord pour connaître l'action + les params attendus. Les params path (ex: id) et le body JSON sont passés dans params.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesNom canonique de l'action (ex: 'rh.employes.create').
paramsNoTous les paramètres mélangés : path params (id, ...), query params (limit, cursor, ...) et body fields. Le serveur route automatiquement selon la spec OpenAPI.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations indicate destructive hint, and description adds parameter routing behavior and the prerequisite, providing useful context beyond 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?

Four concise sentences: purpose, format example, prerequisite, parameter behavior. No fluff, front-loaded.

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

Completeness4/5

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

No output schema, but description covers purpose, parameters, and usage context adequately for a generic execution tool.

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

Parameters4/5

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

Schema description coverage is 100%; description adds value by clarifying the canonical name format and that params contains mixed parameters, slightly beyond schema.

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?

Clarifies the tool executes an eyeot ERP action by canonical name with format examples, distinguishing from sibling tools (specific CRUD actions).

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

Usage Guidelines4/5

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

Explicitly instructs to use eyeot_help first, providing prerequisite guidance, though does not explicitly state when to avoid using it (e.g., when a specific tool exists).

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