Skip to main content
Glama
Sign In

Entogo power-equipment knowledge & tools

by ca.entogo
OverviewDiscussionsAdmin

Hand off to Entogo for a quote

request_quote_handoff
Read-only

Returns the right channel for a request for quotation (RFQ): the transformer configurator deep link (pre-filled with the product name), the contact page, e-mail and phone numbers, office hours and the one-business-day response commitment. This tool stores nothing and sends nothing — the user completes the request on entogo.ca or by e-mail.

Input Schema

NameRequiredDescriptionDefault
productNoProduct name or id the user is interested in
summaryNoOne-paragraph project summary to paste into the form
languageNoLanguage of the buyer — links point to that language edition of the siteen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / language / enum
      Previous value: -[
-  "en",
-  "fr",
-  "es",
-  "ar",
-  "pl",
-  "ro"
-]New value: +[
+  "en",
+  "fr",
+  "es",
+  "ar",
+  "pl",
+  "ro",
+  "ru"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
+  "default": "en",
+  "description": "Language of the buyer — links point to that language edition of the site",
+  "enum": [
+    "en",
+    "fr",
+    "es",
+    "ar",
+    "pl",
+    "ro"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint true and openWorldHint false. The description adds useful context by stating that it stores nothing, sends nothing, and that the user completes the request on entogo.ca or e-mail, and it lists the returned channels and response commitment. It does not discuss authentication or rate limits, so not a 5.

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?

Two sentences, front-loaded with the return payload followed by a clarifying no-side-effect statement. Every sentence earns its place with no repetition or filler.

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 simple read-only handoff tool with three optional parameters, 100% schema coverage, and no output schema, the description is complete enough: it enumerates the returned channels and states the no-storage/no-send contract. Nothing essential for correct invocation is missing.

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 description coverage is 100%, so the baseline is 3. The description only adds that the configurator deep link is pre-filled with the product name; it does not add further meaning for the summary or language parameters beyond what the schema already documents.

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?

States a specific verb 'Returns' and resource 'channel for a request for quotation (RFQ),' clearly distinguishing it from all listed siblings such as get_product, list_products, and search_knowledge. An agent can tell what this tool provides without opening the schema.

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?

The description identifies the relevant situation — a request for quotation — and what the user should do next, giving clear context for when the tool applies. It does not explicitly name excluded cases or alternative sibling tools, so it falls short of the full 5.

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

All Entogo power-equipment knowledge & tools 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