Skip to main content
Glama
Sign In

Netfluid

by io.netfluid.mcp
OverviewDiscussionsAdmin

netfluid__account

Returns public information associated with an account_fk: address, commodity, currency and type @return: a json object

Input Schema

NameRequiredDescriptionDefault
account_fkYes

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

C2.6/5.0
Behavior2/5

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

Annotations are empty, so the description carries the full burden. 'Returns public information' implies a safe read, but there is no mention of authentication, permissions, rate limits, or what happens on an invalid account_fk. The '@return: a json object' clause conveys essentially no behavioral information.

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?

Short and front-loaded, which is good, but the trailing '@return: a json object' is boilerplate that adds no value. The whole description is terse to the point of under-specification rather than genuinely concise.

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 read tool with no annotations and no output schema, the description should at least clarify the parameter and differentiate it from the numerous sibling lookups. It leaves both the input semantics and the sibling routing unresolved.

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 0% and the description only repeats the parameter name 'account_fk' without explaining what it identifies or where it comes from. With a single required parameter undocumented in both schema and prose, the description fails to compensate.

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 ('Returns public information associated with an account_fk') and enumerates the fields returned (address, commodity, currency, type). It is clear on its own, but it does nothing to distinguish itself from near-identical siblings such as netfluid__account_info, netfluid__account_address, or netfluid__account_types.

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 call this versus the many sibling account/wallet tools. No preconditions, no alternatives, no exclusions are mentioned.

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