Skip to main content
Glama

Net Promoter Score Mix

bpj_net_promoter_mix
Read-onlyIdempotent

Compute NPS from promoter, passive and detractor counts and show the shares of promoters and detractors among all respondents.

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": {
      "promoters": "<promoters>",
      "passives": "<passives>",
      "detractors": "<detractors>"
    },
    "name": "bpj_net_promoter_mix"
  }
}

Input Schema

NameRequiredDescriptionDefault
passivesYes
promotersYes
detractorsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description's only added behavior is that it also reports promoter/detractor shares. It does not say how the result behaves in edge cases (e.g. all counts zero) or whether inputs are validated against each other.

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?

One front-loaded sentence with no filler, and the output clause ('show the shares...') is appended efficiently rather than buried. It is slightly dense but every clause earns its place.

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?

For a simple three-integer calculator with full annotation coverage this is close to adequate, and it does mention what is returned even though there is no output schema. However, the NPS scale (-100 to 100) and the underlying formula (promoter share minus detractor share) are never stated, leaving an agent to assume a standard definition.

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%, so the description must carry the burden of parameter meaning, but it only restates the three parameter names ('promoter, passive and detractor counts'). It adds nothing about the score bands (0–6, 7–8, 9–10), the 0–100,000,000 bounds, or the requirement that all three be supplied; that meaning lives only in the schema titles.

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 specific verb and resource ('Compute NPS') plus its inputs (promoter, passive and detractor counts) and its output (shares of promoters and detractors among all respondents). No sibling in the catalog computes NPS, so differentiation is not an issue; the operation is unambiguous.

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?

Usage is only implied: the agent can infer the tool applies when it already has aggregated count data rather than raw survey responses. There is no explicit statement of when not to use it, no note about tools that might handle raw scores, and no mention of alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.