Skip to main content
Glama

Report Unsupported Request

report_unsupported_request

Records that the customer asked for a change this connector has no tool for (for example editing contact-form fields, footer link columns, deleting a site, taking a site offline, restoring a backup). Stores only a short kebab-case capability name (e.g. form-fields) and an optional one-line note in general terms; the note is refused if it contains an email address, phone number or web address, and nothing else from the conversation is stored. Does not change the site. Returns a link to the Zarla editor, where the customer can make the change themselves.

Annotations: read-only=false, destructive=false, idempotent=false, open-world=false. Why: Records that a request could not be served so Zarla can add the capability; appends a note, overwrites nothing (additive, not destructive). Not idempotent: each call records another note. Closed-world.

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": {
      "capability": "<capability>"
    },
    "name": "report_unsupported_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoOne line, general terms only — no names, contact details or web addresses
site_idNoThe site it was about, if known
capabilityYesKebab-case name of the missing capability (e.g. form-fields, footer-links, delete-site, unpublish-site, restore-backup, multi-page-build) — never the customer's content or words
tool_triedNoThe tool that couldn't do it, if one was attempted (e.g. update_block)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses exactly what is persisted (only a kebab-case capability name plus an optional one-line note), a runtime validation rule (notes containing email, phone or web address are refused), that nothing else from the conversation is stored, and that the site is not modified. The annotations already cover the read-only/destructive/idempotent profile, and the description adds substantive behavioral detail on top without contradicting them.

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?

Purpose is front-loaded in the opening clause and each following sentence adds a distinct fact (storage scope, PII refusal, no mutation, return value). It is a dense single paragraph where a short list or line breaks would improve scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations explaining storage or return values, the description fills both gaps by naming the returned editor link and specifying exactly what data leaves the conversation. Nothing an agent needs to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the capability param must be a general kebab-case label (examples 'form-fields'), and the note param carries a rejection rule for PII that the schema only hints at. It stops short of explaining the site_id vs tool_tried interplay.

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

Purpose5/5

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

The first sentence gives a specific verb and resource ('Records that the customer asked for a change this connector has no tool for') and enumerates concrete unsupported cases such as editing contact-form fields, deleting a site and restoring a backup. An agent can immediately distinguish this from write siblings like update_footer or remove_page, which act on supported capabilities.

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?

It states the selecting condition clearly: use when no existing tool can serve the request, with representative examples. The inverse condition ('do not use when a sibling tool can do it') is only implied by 'has no tool for' rather than stated, so it falls short of explicit when-not guidance.

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.