Skip to main content
Glama
Sign In
DEX_MCP

DEX_MCP

Official
by teamviewer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

cached_users_add

Create a new cached user in a DEX tenant. Provide a username, plus optional email and display name, to add the user record.

Instructions

Create a new cached user.

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": {
      "username": "<username>"
    },
    "name": "cached_users_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
usernameYes
displayNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states that a new cached user is created, but does not mention whether creation is idempotent, whether username must be unique, what happens on conflict, whether cached data is persisted, or what response to expect.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no filler and the action verb is front-loaded. It is concise, though it achieves this by omitting useful detail rather than by summarizing rich content.

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?

For a write operation with no annotations and no output schema, this description is incomplete. An agent still cannot determine conflict behavior, return value, or the semantic difference between a cached user and a regular consumer, which are essential for correct invocation.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no parameter meaning at all. It does not mention username, email, or displayName, nor clarify that username is required or what values are expected for email and displayName.

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

Purpose4/5

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

The description identifies a specific action ('Create') and resource ('cached user'), which clearly differentiates it from cached_users_update, cached_users_delete, and cached_users_list. It does not explain what a 'cached user' is, but the verb+resource pairing is unambiguous enough for basic selection.

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?

There is no guidance about when to use this tool versus alternatives such as consumers_add or cached_users_update. No context, prerequisites, or exclusions are provided, leaving the agent to infer usage purely from the name.

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