Skip to main content
Glama

sitekick_binding_choices

Read-onlyIdempotent

List authorized native binding choices by kind and page. Retain the opaque choice token; native IDs are not exposed.

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>"
    },
    "name": "sitekick_binding_choices"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
site_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds one genuinely non-obvious behavioral fact: choices are opaque tokens and native IDs are deliberately withheld, which affects how the agent must handle results. It says nothing about pagination behavior despite a page parameter capped at 49.

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?

Two sentences, zero filler, with the listing scope front-loaded and the token-retention caveat immediately after. Every clause carries information.

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?

An output schema exists, so return shape needn't be described, and the token caveat covers the main result-handling risk. However, for a nested payload with an unannotated enum and a bounded page index, the definition leaves the agent guessing about kind semantics and pagination limits.

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 compensate, and it only re-states the parameter names ("by kind and page"). It never explains what forms/bookings/commerce mean, that page is zero-indexed and capped at 49, or that site_ref scopes the lookup.

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?

Specific verb plus resource: "List authorized native binding choices by kind and page" tells an agent exactly what is returned and the two filter axes. It does not name or contrast with siblings such as sitekick_binding_enroll, so it stops short of full differentiation.

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 or when-not-to-use statement is given, and no alternative (e.g., enroll) is referenced. The agent must infer that this is a pre-enrollment lookup from the word "choices" alone.

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