Skip to main content
Glama

eyeot ERP

by io.github.Termi24
OverviewDiscussionsAdmin

create_opportunity

Créer une opportunité

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesRequest body

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / body / properties / probability
      Added value: +{
+  "maximum": 100,
+  "minimum": 0,
+  "type": [
+    "integer",
+    "null"
+  ]
+}
    • removedInput schema / properties / body / properties / stage / enum
      Removed value: -[
-  "prospect",
-  "qualification",
-  "proposition",
-  "négociation",
-  "gagné",
-  "perdu"
-]
    • addedInput schema / properties / body / properties / stage / maxLength
      Added value: +40
    • addedInput schema / properties / body / properties / stage / minLength
      Added value: +1
  2. First observed

TDQS

C2.2/5.0
Behavior2/5

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

The description does not disclose behavioral traits such as whether the tool returns the created resource's ID, whether it requires specific permissions, or what side effects occur. Annotations are all false, leaving the agent with no additional insight.

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?

While very concise (one phrase), the description is under-specified. It sacrifices usefulness for brevity and does not earn its place as a net improvement over the tool name.

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 lack of output schema and annotations, the description is incomplete. It fails to explain what happens on success (e.g., returns opportunity ID) or any operational constraints.

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?

The input schema covers all parameters with constraints and descriptions for the body object, so schema coverage is high. However, the description adds no further meaning beyond what the schema provides.

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

Purpose2/5

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

The description 'Créer une opportunité' is a tautology of the tool name. It states the tool creates an opportunity but provides no detail to distinguish it from sibling tools like create_quote or create_order.

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 on when to use this tool versus alternatives. There are many sibling tools for creating CRM entities, but the description offers no context for selection.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources