Ad Arch Agents

サービスの一覧を見る

list_services

Read-only

Use this when the user asks what services Ad Arch offers, or what information is needed before requesting a quote. Returns the request types Ad Arch accepts (filming, video production, YouTube, social media, TVer ads, other ad media, design, websites, events, other creative work, other) with the items to confirm before a quote for each type, and the service packages Ad Arch has published, with the deliverables and typical lead time of each (this list can be empty). Optional category filters the service packages only (e.g. 制作 / TVer / SNS / 採用). Does not return prices.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`role`	No	The user's position: company = a business commissioning production or advertising / creator = a videographer, editor or other creator / agency = an advertising agency or production company.
`category`	No	Text to filter the service packages by category (e.g. 制作 / TVer / SNS / 採用).

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No	Notes that apply to the result, in Japanese.
`error`	No	Reason the request could not be answered, in Japanese.
`message`	No	Message for the user, in Japanese.
`needRole`	No	true when the call was made without `role`; nothing else is returned.
`services`	No	Published service packages. Can be empty.
`howToSend`	No
`howWeWork`	No
`hearingRule`	No
`notAvailable`	No	true when the tool is not available for the given role.
`requestKinds`	No	Request types accepted, with the items to confirm before a quote.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 6, 2026

addedInput schema / properties / category / description

Added value: +"Text to filter the service packages by category (e.g. 制作 / TVer / SNS / 採用)."

changedInput schema / properties / role / description

Previous value: -"相手の立場：company＝制作・広告を頼む側の企業／creator＝制作者・クリエイター／agency＝広告代理店・制作会社（同業）。立場によって使えるツールが違う"New value: +"The user's position: company = a business commissioning production or advertising / creator = a videographer, editor or other creator / agency = an advertising agency or production company."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "error": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Reason the request could not be answered, in Japanese."
+    },
+    "hearingRule": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "howToSend": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "howWeWork": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "message": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Message for the user, in Japanese."
+    },
+    "needRole": {
+      "description": "true when the call was made without `role`; nothing else is returned.",
+      "type": "boolean"
+    },
+    "notAvailable": {
+      "description": "true when the tool is not available for the given role.",
+      "type": "boolean"
+    },
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Notes that apply to the result, in Japanese."
+    },
+    "requestKinds": {
+      "description": "Request types accepted, with the items to confirm before a quote.",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "askFor": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "kind",
+          "name",
+          "askFor"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "services": {
+      "description": "Published service packages. Can be empty.",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "category": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "deliverables": {
+            "items": {
+              "additionalProperties": {},
+              "properties": {
+                "name": {
+                  "anyOf": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                },
+                "qty": {
+                  "anyOf": [
+                    {
+                      "type": "number"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                },
+                "spec": {
+                  "anyOf": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                },
+                "unit": {
+                  "anyOf": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "id": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "leadTime": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "name": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "tagline": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "tip": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "whatWeDo": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 24, 2026

changedInput schema / properties / role / description

Previous value: -"相手の立場（最初に1問だけ選択肢で聞いた答え）：company＝制作・広告を頼む側の企業／creator＝制作者・クリエイター／agency＝広告代理店・制作会社（同業）。必ず付ける"New value: +"相手の立場：company＝制作・広告を頼む側の企業／creator＝制作者・クリエイター／agency＝広告代理店・制作会社（同業）。立場によって使えるツールが違う"

First observedSep 24, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safe-read profile (readOnlyHint, non-destructive, closed-world), and the description adds real behavioral detail beyond them: the package list may be empty, the category parameter narrows packages only, and prices are deliberately excluded. These are useful expectations an agent could not infer from the schema.

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?

The usage trigger is front-loaded and the long middle sentence is dense with genuinely useful return-content detail rather than filler. The enumeration of request types is somewhat verbose but earns its place by telling the agent what to expect.

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?

For a two-parameter read tool with an output schema and safety annotations, the description is nearly complete: it covers when to call it, what returns, and the key exclusion (no prices). The only gap is silence on the role parameter's effect, which the schema does document.

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 both role and category are already documented, and the description's note that category filters service packages only largely restates the schema wording. The role parameter is not mentioned at all in the description, so no meaning is added beyond the schema baseline.

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 and resource (list services Ad Arch offers) and enumerates exactly what comes back: accepted request types with pre-quote confirmation items, plus published service packages with deliverables and lead times. It is far more precise than the title alone, though it never explicitly contrasts itself with siblings like list_ad_media or get_tver_ad_monthly_rate.

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 a clear trigger: use when the user asks what services are offered or what information is needed before requesting a quote, which implicitly routes the quote flow to submit_quote_request. No explicit when-not-to-use or named alternatives, so it stops short of a 5.

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

All Ad Arch Agents 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?