Skip to main content
Glama
Sign In
mcp-remnawave

mcp-remnawave

by Nurullaev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

billing_provider_update

Update billing provider details by UUID. Change the name or description to keep provider information current.

Instructions

Update a billing provider

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": {
      "uuid": "<uuid>"
    },
    "name": "billing_provider_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew name
uuidYesProvider UUID
descriptionNoNew description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description bears full responsibility for disclosing behavior. It only says 'Update', implying mutation, but provides no details on side effects, permission requirements, reversibility, or what happens to unmentioned fields. This is a significant gap for a mutation tool.

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 description is a single sentence with no wasted words, but it is extremely minimal. It conveys the verb and resource but lacks any structural elaboration. It is not 'under-specified' to the point of a tautology, but it is barely informative.

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 simple update tool with three parameters and no output schema, the description provides almost no context beyond the action word. It omits details about how the provider is identified (uuid is in schema), what fields can be updated (already in schema), and any behavioral notes. Given the lack of annotations, this is incomplete for safe usage.

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

Parameters3/5

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

Schema description coverage is 100%, so the input schema already documents all three parameters (name, description, uuid). The description adds no extra meaning beyond what the schema provides, but the schema does the heavy lifting, so a baseline of 3 is appropriate.

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 states the verb 'Update' and the resource 'billing provider', making the core action clear. It distinguishes from sibling read/delete/create tools by the verb, though it does not explicitly differentiate from other update tools like billing_node_update.

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?

No guidance is given on when to use this tool versus alternatives such as billing_provider_create or billing_provider_delete. There is no mention of context, prerequisites, or conditions that would select this tool.

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

Deploy Server

Other Tools