Skip to main content
Glama
Sign In
DEX_MCP

DEX_MCP

Official
by teamviewer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

consumers_add

Add a new consumer to the DEX tenant with a unique alphanumeric name and configure its enabled state, endpoints, and concurrency limit. Consumer write permission is required.

Instructions

Create a Consumer. Name must be alphanumeric+underscore only, unique. System consumers cannot be created. Requires 'Write' on 'Consumer'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "maximumSimultaneousInFlightInstructions": "<maximumSimultaneousInFlightInstructions>"
    },
    "name": "consumers_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
isEnabledNo
applicationUrlNo
offloadTargetUrlNo
instructionHandlerUrlNo
offloadUseWindowsAuthNo
offloadPostTimeoutSecondsNo
maximumSimultaneousInFlightInstructionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It meaningfully discloses that name must be alphanumeric+underscore only and unique, that system consumers cannot be created, and that Write permission on Consumer is required. It stops short of describing return values or failure modes, but the stated constraints add substantial behavioral context.

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?

Three terse sentences with no filler. The core action is front-loaded, and every sentence adds operational value: creation intent, name constraints, and permission requirement.

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 no annotations, no output schema, and 0% schema coverage, the description is the only source of guidance but only covers the name parameter and permission. It omits semantics for the required maximumSimultaneousInFlightInstructions, all optional parameters, and success/error behavior, so it is not complete enough to invoke confidently.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It only explains the 'name' parameter's format and uniqueness requirement; the required 'maximumSimultaneousInFlightInstructions' and the six optional parameters are left completely unexplained. This is weak compensation for an eight-parameter 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?

The description uses a specific verb and resource ('Create a Consumer') and is clearly distinguishable from sibling tools like consumers_list, consumers_get_by_id, consumers_update, and consumers_delete. The naming constraints further clarify the operation's identity.

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 makes the usage context explicit: call this tool to create a Consumer, and it notes the required 'Write' permission. It does not explicitly mention alternatives like consumers_update for existing records, but for a create operation the context is clear enough.

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

Deploy Server

Other Tools