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

TableJSON 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

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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.4/5.0

Behavior4/5

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

Annotations are empty, so the description carries the burden and does meaningful work: it discloses latency ('up to 30 seconds'), the required post-signup action (direct human to KYC URL), and the retry path (wallet_kyc_session_create). It could add more about side effects of creating a customer, but the core behavioral contract is covered.

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 front-loaded with purpose and the parameter documentation is dense but valuable. The exact sentence 'Automated signup for new customers' appears twice, which is unnecessary redundancy, but it does not meaningfully hurt usability.

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 an 8-parameter mutation with no annotations and an output schema, the description covers the full input semantics, latency, and downstream KYC workflow. The only minor gap is not explicitly saying that the KYC URL is part of the return payload, though the output schema helps cover return expectations.

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?

With 0% schema description coverage, the description fully compensates: every parameter gets meaning, including secret constraints and generation suggestion, PIN format, E.164 mobile format, currency selection logic (7=ZAR for South Africans, 3=USD otherwise), defaults for app_id/org_id, and a conditional rule for customer_referral_code.

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?

Description opens with a concrete action ('Automated signup for new customers') and adds an explicit agent directive: use as the preferred method to sign up human customers. The 'human customers' qualifier distinguishes it from the sibling netfluid__automated_agent_signup without ambiguity.

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?

It clearly states when to use the tool ('preferred method to signup human customers') and routes follow-up KYC retries to wallet_kyc_session_create. It does not explicitly state exclusions such as using automated_agent_signup for non-human signups, but the human-customer scoping supplies enough context.

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?