Skip to main content
Glama

日本向け広告文の表現チェック

check_japanese_ad_copy
Read-onlyIdempotent

Mechanically flag potentially misleading Japanese advertising claims with severity, quoted context, and alternative wording. This is not a legal determination. 日本向け広告・LPの表現を機械的に点検します。

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": {
      "text": "<text>"
    },
    "name": "check_japanese_ad_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely non-redundant behavior: results include severity levels, quoted context, and suggested alternative wording, and the 'not a legal determination' caveat tells the agent how much authority to grant the findings.

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?

Two compact sentences: the capability and output shape are front-loaded, then the legal disclaimer. The Japanese sentence largely restates the English one, which is mild redundancy, but it usefully serves Japanese-speaking agents and the overall length is well within proportion.

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?

An output schema exists, so return values need no further explanation, and with one required string parameter the surface area is small. The definition covers capability, output shape, and the limits of its authority; the only gap is input expectations, such as whether non-Japanese or mixed-language text is handled.

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 0% for the single 'text' parameter, so the description must carry the meaning — and it does establish that the input is Japanese advertising or landing-page copy, which is real semantic content beyond the bare string type. It still does not address granularity (whole ad vs. single phrase), expected language, or how the 20,000-character limit should be used.

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?

The description names a specific verb ('flag'), a specific resource ('Japanese advertising claims'), and even the shape of the output (severity, quoted context, alternative wording). It does not need to distinguish itself from the sibling tools, which are plainly unrelated (automation spec/savings), so the only thing keeping this from a 5 is the absence of any explicit scoping boundary against other checks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Mechanically flag' plus 'This is not a legal determination' implies a first-pass screening use case and warns against treating output as a compliance ruling, which is useful implied guidance. However, there is no explicit statement of when to call this versus doing nothing, no prerequisite (e.g., copy must be in Japanese), and no exclusion beyond the legal disclaimer.

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