Tuqo

Allow email addresses

add_site_access_emails

Destructive

Add many addresses to the email allowlist in one call, separated by newlines, commas or semicolons. Duplicates and existing entries are skipped, invalid ones are returned separately: partial success is normal. Labels are not set here (a comma would split them): use set_site_access_email_label afterwards.

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": {
      "site_id": "<site_id>",
      "emails": "<emails>"
    },
    "name": "add_site_access_emails"
  }
}

Input Schema

Name	Required	Description	Default
`emails`	Yes	Addresses, one per line or comma-separated
`site_id`	Yes	UUID of the site

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 7, 2026

changedInput schema / properties / emails / description

Previous value: -"Адреса списком: по одному в строке или через запятую"New value: +"Addresses, one per line or comma-separated"

changedInput schema / properties / site_id / description

Previous value: -"UUID сайта"New value: +"UUID of the site"

First observedSep 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only flag the operation as a non-read, destructive mutation; the description adds substantial context beyond them: duplicates and existing entries are skipped, invalid entries are returned separately, and partial success is the normal outcome. That is exactly the behavior an agent needs to interpret results and retry logic.

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?

Four tight sentences, front-loaded with the core action and scope, then behavioral caveats, then the routing note. Nothing is padded and every sentence carries information.

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, the description correctly discloses what comes back (invalid addresses returned separately) and the partial-success semantics. Together with the sibling routing note, an agent has everything needed to call and interpret this tool.

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% (baseline 3), but the description adds meaning beyond the schema's 'one per line or comma-separated' by also allowing semicolons, and explains that labels cannot be set at this stage because a comma would split them — a delimiter-level detail the schema does not convey.

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?

States a specific verb and resource — adding many addresses to the email allowlist in one call — and the bulk framing implicitly distinguishes it from the singular sibling add_site_access_email. An agent can tell what it does without opening the schema.

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?

Clearly frames the bulk use case ('many addresses ... in one call') versus the singular sibling, and explicitly routes the agent to set_site_access_email_label afterwards for labels, with the reason (a comma would split them). No explicit when-not guidance or named single-address alternative, so not a 5.

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

All Tuqo tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.