Nikola Dikic - Full-Stack Developer, WordPress, WooCommerce, ERP Integrations

submit_urgent_request

Report a site that is broken now — checkout failing, payments declined, a critical error, a white screen, locked out of wp-admin, an update that broke the site, a hack or a malware warning. Triaged the same day, within eight hours, weekends included, across European, US, Canadian and Australian hours. Submits immediately: there is no confirmation email to wait for, because friction on an emergency is friction in the wrong place. Ask the person before calling this, and send a real phone number — the reply comes by phone or WhatsApp.

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": {
      "name": "<name>",
      "phone": "<phone>",
      "site": "<site>",
      "message": "<message>"
    },
    "name": "submit_urgent_request"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Their name.
`site`	Yes	The address of the site that is broken.
`email`	No	Optional. If given, they get a written acknowledgement too.
`phone`	Yes	A number they can actually be reached on, with country code. The reply comes this way.
`message`	Yes	What is happening, in their words. Include the exact error text if there is any.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 30, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only declare the mutation profile (not read-only, not idempotent, non-destructive). The description adds substantial non-obvious behavior: immediate submission with no confirmation email, same-day/eight-hour triage including weekends and multiple time zones, and that the reply arrives by phone or WhatsApp.

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?

Front-loaded with the purpose, then triage SLA, then submission behavior and the consent/phone caveat. The long symptom list is informative but slightly padded; still, every sentence carries actionable content.

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?

Covers what the tool does, how fast, how the reply comes back, and the consent prerequisite. With full schema coverage and no output schema, the remaining gap is only the absence of an explicit non-urgent alternative route.

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%, so the schema already documents all five parameters, including the phone country-code and optional-email semantics. The description only reinforces the phone requirement ('send a real phone number'), adding little beyond the schema.

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?

Names a specific action (submit an urgent/broken-site request) and enumerates the concrete conditions that qualify it — checkout failure, hack, lockout, white screen. This is clearly distinguishable from non-urgent siblings like submit_project_inquiry or request_consultation.

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?

Gives real usage context: it is for sites broken 'now' with same-day triage, and it explicitly instructs the agent to 'ask the person before calling this' and to supply a real phone number. It doesn't explicitly name the non-urgent alternative to route to, which keeps it from a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nikola Dikic - Full-Stack Developer, WordPress, WooCommerce, ERP Integrations tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?