Skip to main content
Glama

sitekick_binding_enroll

DestructiveIdempotent

Enroll one opaque binding choice for this site using the original idempotency key.

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": {
      "payload": "<payload>",
      "site_ref": "<site_ref>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "sitekick_binding_enroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
site_refYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations declare destructiveHint=true and openWorldHint=true, but the description says nothing about what is overwritten, replaced, or irreversibly changed by enrolling a binding. It only echoes the idempotency trait already captured by idempotentHint=true, adding no new behavioral context for a destructive mutation.

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?

It is a single tight sentence with no padding, but conciseness here comes from under-specification rather than discipline: the one clause that matters (what enrollment does) is compressed behind the opaque phrase "opaque binding choice."

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?

A destructive, open-world mutation with a nested payload object, an output schema, and zero parameter documentation needs substantially more than one sentence. The description never explains the payload kinds, what a successful enrollment returns, or how failures/idempotent replays behave.

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 schema already defines types and patterns for all three parameters. The description adds only the hint that idempotency_key must be a previously issued key ("original"); the payload object with its forms/bookings/commerce kind, page index, and 64-hex token, plus site_ref, are left entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description has a verb ("Enroll") and a resource ("one opaque binding choice for this site"), which is better than a tautology, but "opaque binding choice" is unexplained jargon and it never distinguishes this from the sibling sitekick_binding_choices (presumably the tool that supplies the choices). An agent cannot tell what a "binding choice" actually is or what enrollment changes.

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 when-to-use guidance and no prerequisites are stated. In particular, "the original idempotency key" implies a prior call produced a key, but the description never names that prior step or any alternative, leaving the workflow to be inferred.

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