Netfluid

netfluid__automated_signup

Automated signup for new customers. AI should use this tool as the preferred method to signup human customers.

Automated signup for new customers. Process can take up to 30 seconds. Once completed direct the human customer to the kyc url for them to complete the identity verification process. Should the human need more tries at identity verification, call wallet_kyc_session_create @param secret: A secret, minimum 8 characters, must be unique system-wide. This is typically the customer username, but private. Suggestion: Generate 3 natural language words, concatenated, or prompt the human for 3 words, something that the human can remember. @param pin: The 5 digit PIN associated with the wallet. Can be any random 5 numbers, but perhaps use something that is meaningful to the human or prompt them for it. @param email: The customers email address. @param mobile: The customers mobile phone number, in e164 format, e.g. 27821234567 (no +) @param currency_fk: The currency of the first account, if the human is South African, use 7 (ZAR) for everyone else use 3 (USD) @param app_id: The app id for this customer group, default is 1 (Netfluid) @param org_id: The organisational id for this customer group, default is 0 (Netfluid) @customer_referral_code: The customer's referral code, this cannot be blank if app_id != 1

@return: a json object

Input Schema

Name	Required	Description	Default
`pin`	Yes
`email`	Yes
`app_id`	No
`mobile`	Yes
`org_id`	No
`secret`	Yes
`currency_fk`	No
`customer_referral_code`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026
- changedOutput schema / (root)
```
Previous value: -{
-  "type": "object"
-}New value: +null
```

Changed1 schema field changedSep 15, 2026

addedInput schema / properties / customer_referral_code

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": ""
+}

Changed2 schema fields changedSep 15, 2026

addedInput schema / properties / app_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": 1
+}

addedInput schema / properties / org_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": 0
+}

AddedJul 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does add meaningful behavior: the call can take up to 30 seconds, it produces a KYC url the human must be sent to, and the retry path goes through wallet_kyc_session_create. It still omits auth/permission requirements and what happens on failure or duplicate signup, so it is not fully complete.

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

Conciseness3/5

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

The opening line 'Automated signup for new customers.' is duplicated verbatim immediately after the preferred-method sentence, which is pure redundancy. The rest is front-loaded and informative, but the repetition wastes space in an otherwise long block.

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?

Handles 8 parameters well and gives the downstream KYC workflow, but there is no output schema and the return value is described only as 'a json object' — it never states that the returned object contains the KYC url the caller is told to hand to the customer. Naming that field would close the remaining gap.

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

Parameters5/5

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

Schema description coverage is 0%, and the description compensates fully: min-8-character unique 'secret' generation advice, 5-digit 'pin', e164 'mobile' with a concrete example, currency_fk mapping (7=ZAR, 3=USD), default app_id/org_id values, and the conditional constraint that customer_referral_code cannot be blank when app_id != 1.

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?

States a specific verb and resource ('Automated signup for new customers') and distinguishes the human path from the agent path by scoping it to 'human customers' (vs. sibling netfluid__automated_agent_signup). It does not name that sibling explicitly, so the differentiation is inferred rather than stated.

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?

Explicitly marks itself as 'the preferred method to signup human customers' and gives a follow-up routing rule: after completion, direct the customer to the KYC url, and if more verification tries are needed, call wallet_kyc_session_create. Clear context and one named alternative, but no explicit when-NOT-to-use exclusions.

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

All Netfluid tools Inspect

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

Need Help?