Ad Arch Agents

TVer広告の月額の目安を調べる

get_tver_ad_monthly_rate

Read-only

Use this when the user asks how much a TVer ad costs in a specific Japanese prefecture or city. TVer is a Japanese ad-supported TV streaming service. Given a prefecture and city, returns the lowest monthly rate for that area (JPY, excluding tax, guide only), the minimum campaign length and the area's population. For areas where the rate is quoted individually, no figure is returned. allCities: true returns only the names and populations of the municipalities in the prefecture, ordered by population, without rates. Does not return per-plan rates or audience estimates. Video production costs are not included.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	City, ward, town or village, in Japanese (e.g. 高松市). If omitted, the most populous city in the prefecture is used.
`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.
`allCities`	No	Set true to list the municipalities in the prefecture (names and populations only, no rates).
`prefecture`	Yes	Japanese prefecture, in Japanese including the suffix (e.g. 香川県).

Output Schema

TableJSON Schema

Name	Required	Description
`area`	No
`note`	No	Notes that apply to the result, in Japanese.
`areas`	No	With allCities: the municipalities in the prefecture, ordered by population. No rates.
`error`	No	Reason the request could not be answered, in Japanese.
`rules`	No
`message`	No	Message for the user, in Japanese.
`needRole`	No	true when the call was made without `role`; nothing else is returned.
`minMonths`	No	Minimum campaign length in months.
`planTypes`	No
`howToOrder`	No
`population`	No
`prefecture`	No
`monthlyFrom`	No
`notAvailable`	No	true when the tool is not available for the given role.
`monthlyFromYen`	No	Lowest monthly rate in JPY, excluding tax. null when the rate is quoted individually.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare a safe read-only, non-destructive, non-open-world operation, and the description adds substantial behavioral context: rates are JPY excluding tax and guide-only, no figure is returned where pricing is quoted individually, allCities returns only names/populations ordered by population, and production costs are excluded.

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?

Five tight sentences, front-loaded with the trigger and core return contract, with exclusions trailing. No filler or repetition of the title.

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 an output schema present, the description need not detail return shape, yet it still communicates the return contract, edge case (no figure for individually quoted areas), and limits. Nothing an agent needs to select or invoke it correctly is missing.

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%, so the baseline is 3, but the description goes beyond the schema by stating that allCities results are ordered by population and that omitting city defaults to the most populous municipality. It adds real meaning, though role semantics are left entirely to 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?

States a specific verb, resource, and scope: returns the lowest monthly ad rate for a TVer ad in a given prefecture/city, plus minimum campaign length and population. The TVer definition and the not-returned exclusions make it clearly distinguishable from siblings like list_ad_media or find_ad_awards.

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 ('Use this when the user asks how much a TVer ad costs in a specific Japanese prefecture or city') and clarifies the allCities variant's purpose. It lists exclusions (per-plan rates, audience estimates, production costs) but does not name alternative sibling tools for those adjacent questions.

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?