Skip to main content
Glama
Sign In
DEX_MCP

DEX_MCP

Official
by teamviewer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

authentication_authenticate_instruction

Submit a one-time token to complete two-factor authentication for an instruction. Only the instruction creator can use this to verify identity and authorize the action.

Instructions

Submit a one-time token for Instruction Two-Factor Authentication. Only the instruction creator can call this.

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": {
      "instructionId": "<instructionId>",
      "token": "<token>"
    },
    "name": "authentication_authenticate_instruction"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesOne-time token
instructionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It does disclose that the token is one-time and that caller identity is restricted, but it does not explain what happens on success or failure, whether the token is consumed, or how the instruction state changes after authentication.

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 short sentences with no filler. The primary action is front-loaded, and the access restriction earns its place by preventing misuse.

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 security-sensitive two-factor authentication operation, the description is thin. It lacks the expected success/failure behavior, token validity details, and enough guidance for an agent to understand the full authentication flow, especially with no output schema to clarify return values.

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 only 50%: token is documented as 'One-time token' but instructionId has no description. The tool description does not clarify what instructionId refers to or how it relates to the token, so it fails to compensate for the undocumented parameter.

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 states a clear action ('Submit a one-time token') and a specific resource ('Instruction Two-Factor Authentication'). It also adds a scope constraint ('Only the instruction creator can call this'), which helps distinguish this from the related sibling authentication_authenticate_scheduled_instruction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives an access precondition ('Only the instruction creator can call this') and implies it is for authenticating an instruction rather than a scheduled instruction, but it never explicitly says when to use this tool versus the scheduled-instruction sibling or describes the surrounding authentication flow.

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