Skip to main content
Glama
Sign In
DEX_MCP

DEX_MCP

Official
by teamviewer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

consumers_list

Retrieve a complete list of consumers from the 1E DEX tenant to enable user management and oversight. Use this tool to identify and access all consumer records for streamlined operations.

Instructions

Return all Consumers. Requires 'Read' on 'Consumer'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "consumers_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/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 explicitly states the required permission ('Read' on 'Consumer') and implies a read-only side-effect-free operation. It does not discuss pagination or response format, but for a simple list-all tool, the permission note is meaningful added 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?

The description is two sentences with no filler. The primary action is front-loaded in the first sentence, and the permission requirement is the only additional sentence. Every word contributes.

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?

For a zero-parameter list tool, the description covers the essential invocation context: what it returns and the required permission. It could mention response shape or pagination, but the absence of an output schema is less critical when the operation is simply returning all Consumers.

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?

The tool has zero parameters and schema coverage is 100%, so there are no parameter semantics to clarify. The description adds no parameter detail, but the baseline for zero-parameter tools is appropriate since nothing is left undocumented.

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 the specific verb 'Return' with the resource 'all Consumers', clearly indicating a list-all operation. This distinguishes it from sibling tools like consumers_get_by_id, consumers_get_by_name, and consumers_search.

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 word 'all' provides clear context that this tool is for retrieving the full set of consumers rather than a filtered or single record. It does not explicitly name alternatives or exclusions, but for a zero-parameter list, the usage context is reasonably clear.

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