Skip to main content
Glama

Xonta MAX

max_check_webhook_secret

Read-onlyIdempotent

Check a MAX webhook secret against the rules (5-256 chars, A-Z a-z 0-9 _ -) or generate a strong one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "max_check_webhook_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG)
secretNoSecret to check; omit to generate a new one

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 closed-world scope, so the safety profile is covered. The description adds the concrete validation contract (5-256 chars, A-Z a-z 0-9 _ -) and the generation mode, which is real added context. It does not disclose what the check returns (pass/fail details) or the properties of the generated secret, so the added disclosure is partial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the primary action and puts the constraint set in parentheses, with the alternate mode last. No filler, nothing repeated.

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, so the description is the only place to learn the return shape, and it never says whether the check returns a boolean, a violation reason, or a generated string. Given a simple two-optional-parameter tool this is a moderate gap rather than a blocker, and the parameter documentation is otherwise complete.

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 coverage is 100%: both `secret` and `lang` are documented, including 'omit to generate a new one' and language defaults. The description only restates the omit-to-generate behavior and adds the character rules, which the schema does not spell out, so value added is marginal — the 3 baseline applies.

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 gives a specific verb and resource ('Check a MAX webhook secret') and adds the dual mode ('or generate a strong one'), so an agent immediately understands both outputs. It does not explicitly contrast with any sibling, but the siblings listed (verify_signature, check_ad_post, etc.) are far enough apart that no differentiation is strictly needed.

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?

The 'omit to generate a new one' clause functions as an implied when-to-use rule for the alternate mode, which is genuinely helpful. However, there is no stated when-not or named alternative for related tasks such as signature verification, so guidance is inferred rather than explicit.

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.