Ad Arch Agents

補助金を探す

find_subsidies

Read-only

Use this when the user asks about public subsidies or grants in Japan that may cover advertising or video production costs. Returns currently open national and local programs listed on jGrants (the Japanese government's subsidy portal) whose eligible costs include, or may include, advertising or video production. Programs confirmed to cover advertising costs come first, then by nearest deadline. Can be filtered by prefecture (nationwide programs are always included) and industry. Results are for reference only; eligibility and award are not guaranteed.

Input Schema

TableJSON Schema

Name	Required	Description
`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.
`limit`	No	Maximum number of results. Default 10, maximum 20.
`industry`	No	Industry keyword in Japanese (e.g. 製造業 / 宿泊業 / 小売業).
`prefecture`	No	Japanese prefecture, in Japanese (e.g. 香川県). Nationwide programs are always included.

Output Schema

TableJSON Schema

Name	Required	Description
`asOf`	No
`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.
`subsidies`	No	Matching programs. Can be empty.
`notAvailable`	No	true when the tool is not available for the given role.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 6, 2026

changedInput schema / properties / industry / description

Previous value: -"業種の言葉（例: 製造業／宿泊業／小売業）"New value: +"Industry keyword in Japanese (e.g. 製造業 / 宿泊業 / 小売業)."

changedInput schema / properties / limit / description

Previous value: -"既定10・最大20"New value: +"Maximum number of results. Default 10, maximum 20."

changedInput schema / properties / prefecture / description

Previous value: -"例: 香川県（全国の制度は常に含む）"New value: +"Japanese prefecture, in Japanese (e.g. 香川県). Nationwide programs are always included."

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": {
+    "asOf": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "error": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Reason the request could not be answered, in Japanese."
+    },
+    "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."
+    },
+    "subsidies": {
+      "description": "Matching programs. Can be empty.",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "adCost": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "areas": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "deadline": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "institution": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "maxLimitYen": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "reason": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "subsidyRate": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "title"
+        ],
+        "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

A4.3/5.0

Behavior4/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, so the description adds the behavioral layer that matters: ordering rules (confirmed advertising coverage first, then nearest deadline), prefecture filtering behavior (nationwide programs always included), and an explicit no-guarantee disclaimer. It doesn't discuss rate limits, data freshness, or pagination.

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?

Front-loaded with the trigger condition, then scope, source, ranking rules, filters, and disclaimer in four dense sentences with no filler. Every sentence carries information an agent needs to decide whether and how to call it.

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?

An output schema exists and annotations cover the safety profile, so the description need not explain return values. It nonetheless supplies the source (jGrants), ranking logic, filter semantics, and a confidence caveat, leaving no practical gap for correct invocation.

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 four parameters, including the nationwide-always-included note. The description reinforces the prefecture/industry filtering and adds ordering semantics, but says nothing about the `role` parameter or the `limit` default, so it stays at the baseline.

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 (find) and resource (public subsidies/grants in Japan), with a narrow scope qualifier: programs whose eligible costs include advertising or video production. It is clearly distinguishable from siblings like find_ad_awards or list_services.

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?

Opens with an explicit trigger condition ("Use this when the user asks about public subsidies or grants in Japan that may cover advertising or video production costs"), which is strong, actionable context. It does not name a when-not case or an alternative tool, but no sibling overlaps this niche enough to require that.

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?