Skip to main content
Glama

Market Brew

Preview an account-management command

preview_account_management_command
Read-onlyIdempotent

Use this when an admin asks what an account-management change would do. It describes action-level impact without execution or arbitrary payloads. Admin accounts only.

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": {
      "body": "<body>"
    },
    "name": "preview_account_management_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesAction-level preview metadata. No payload or execution.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / body / additionalProperties
      Previous value: -{}New value: +false
    • changedInput schema / properties / body / description
      Previous value: -"Account command to preview without execution."New value: +"Action-level preview metadata. No payload or execution."
    • addedInput schema / properties / body / properties
      Added value: +{
      +  "action": {
      +    "enum": [
      +      "customer.create",
      +      "customer.activate",
      +      "customer.deactivate",
      +      "license.deactivate",
      +      "subscription.cancel",
      +      "invoice.void",
      +      "invoice.write_off",
      +      "payment.refund",
      +      "credit.create"
      +    ],
      +    "type": "string"
      +  },
      +  "effectiveDate": {
      +    "format": "date",
      +    "type": "string"
      +  },
      +  "reason": {
      +    "maxLength": 200,
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "seoengCustomerId": {
      +    "anyOf": [
      +      {
      +        "exclusiveMinimum": 0,
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      {
      +        "pattern": "^[1-9][0-9]{0,17}$",
      +        "type": "string"
      +      }
      +    ]
      +  },
      +  "targetId": {
      +    "maxLength": 128,
      +    "minLength": 1,
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / body / required
      Added value: +[
      +  "action",
      +  "reason"
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds non-redundant context: it performs no execution, accepts no arbitrary payloads, and is restricted to admin accounts. It omits what the preview response actually contains, which keeps it below a 5.

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?

Three short sentences with the trigger condition front-loaded and no filler. The admin-only restriction is tacked on at the end rather than integrated, a minor structural nit rather than wasted text.

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?

With an enum of nine supported actions and a nested body object, the tool is moderately complex, but the schema carries all parameter detail and the annotations carry the safety profile. The one remaining gap is that, with no output schema, the description never indicates what a 'preview' returns (per-action diff, warnings, or just a description), leaving return-shape expectations partly inferred.

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% and the single nested body object already documents action, reason, targetId, effectiveDate, and customer id. The description restates the 'action-level, no payload' framing already present in the schema rather than adding new parameter meaning. Baseline 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 names a specific capability: previewing the impact of an account-management change without executing it. It goes beyond the title by specifying 'action-level impact' and 'no arbitrary payloads'. It does not differentiate from a hypothetical execute/apply counterpart by name, but the preview-versus-execute distinction 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The opening sentence gives a concrete trigger: 'Use this when an admin asks what an account-management change would do.' The 'without execution' clause implicitly routes actual mutations elsewhere. There is no explicit when-not clause, but the use case is clearly bounded.

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.

Resources