Skip to main content
Glama
Sign In

Netfluid

by io.netfluid.mcp
OverviewDiscussionsAdmin

paywall__customer_create

Creates a customer using the unique identifier (session_key). @param identifier: The customer's unique identifier, typically the session_id @param wallet_fk: The Netfluid wallet_fk to assign to the new customer, defaults to 0, can be set later @param account_fk: The Netfluid account_fk to assign to the new customer, defaults to 0, can be set later @param subscription_type_fk: The database subscription type, defaults to 1 the freemium subscription @return: a json object, containing the customer id in the "values" object

Input Schema

NameRequiredDescriptionDefault
wallet_fkNo
account_fkNo
identifierYes
subscription_type_fkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "type": "object"
-}New value: +null
  2. Added

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses defaults (wallet_fk/account_fk default to 0 and can be set later; subscription_type_fk defaults to 1, freemium) and the return shape, but says nothing about auth requirements, duplicate-identifier handling, or side effects of creating against Netfluid fks.

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?

Docstring-style but front-loaded with the core purpose, followed by structured @param tags that each carry distinct information. Little waste; the only slightly redundant element is restating defaults that also appear in the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description does explain the return (a JSON object with the customer id in the 'values' object), which is valuable. However, for a create tool with zero annotation coverage, key operational details such as permission needs and behavior on duplicate identifiers are missing, leaving it only adequate.

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?

Schema description coverage is 0%, so the description must compensate, and it does: all four parameters are documented, including identifier as the unique session id, the fk assignments, and the default value and meaning (freemium) of subscription_type_fk. It adds meaning well beyond the bare integer/string types in the schema.

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 opens with a clear verb+resource: 'Creates a customer using the unique identifier (session_key).' This distinguishes it from read-side siblings like paywall__customer_find. It does not explicitly name an alternative or contrast, but the create semantics are unambiguous.

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 on when to use this tool versus alternatives such as customer_find or the various netfluid signup tools, nor any stated prerequisites or the idempotency behavior if the identifier already exists. The only contextual hint is that wallet_fk and account_fk 'can be set later,' implying minimal setup to create.

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

All Netfluid toolsInspect
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