Skip to main content
Glama

Ad Arch Agents

広告賞を探す

find_ad_awards
Read-only

Use this when the user asks which advertising awards they can enter, or when entries open. Returns advertising awards and their next entry period (open now / expected next), with the organizer, categories, entry fee and eligibility where known. Regional awards are returned only when a matching prefecture is given, and are listed first. International awards are returned only when includeInternational is true. category is one of: TVCM / WEB動画 / ラジオCM / 新聞 / 雑誌 / OOH交通 / デジタルWeb / PR / BtoB / キャンペーン総合 / デザイン / パッケージ / 学生 / その他. Dates are for reference only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoThe user's position: company = a business commissioning production or advertising / creator = a videographer, editor or other creator / agency = an advertising agency or production company.
limitNoMaximum number of results. Default 15, maximum 30.
categoryNoAward category to filter by.
openOnlyNoSet true to return only awards accepting entries now.
prefectureNoJapanese prefecture, in Japanese (e.g. 香川県). Adds the regional awards for that prefecture.
includeInternationalNoSet true to include international awards. Default false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoNotes that apply to the result, in Japanese.
errorNoReason the request could not be answered, in Japanese.
awardsNoMatching awards. Can be empty.
messageNoMessage for the user, in Japanese.
needRoleNotrue when the call was made without `role`; nothing else is returned.
notAvailableNotrue when the tool is not available for the given role.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Award category to filter by."
    • addedInput schema / properties / includeInternational / description
      Added value: +"Set true to include international awards. Default false."
    • changedInput schema / properties / limit / description
      Previous value: -"既定15・最大30"New value: +"Maximum number of results. Default 15, maximum 30."
    • changedInput schema / properties / openOnly / description
      Previous value: -"今受付中のものだけ"New value: +"Set true to return only awards accepting entries now."
    • addedInput schema / properties / prefecture / description
      Added value: +"Japanese prefecture, in Japanese (e.g. 香川県). Adds the regional awards for that prefecture."
    • 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": {
      +    "awards": {
      +      "description": "Matching awards. Can be empty.",
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "categories": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "eligibility": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "entryWindow": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "fee": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "organizer": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "region": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "scope": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "url": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          }
      +        },
      +        "required": [
      +          "name"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "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."
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / role / description
      Previous value: -"相手の立場(最初に1問だけ選択肢で聞いた答え):company=制作・広告を頼む側の企業/creator=制作者・クリエイター/agency=広告代理店・制作会社(同業)。必ず付ける"New value: +"相手の立場:company=制作・広告を頼む側の企業/creator=制作者・クリエイター/agency=広告代理店・制作会社(同業)。立場によって使えるツールが違う"
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is already known. The description adds meaningful ordering semantics ('regional awards are listed first'), scoping behaviour for regional and international results, and a caveat that dates are for reference only. It does not describe pagination or the exact shape of the returned entry-period object, but with an output schema and annotations covering the rest, this is strong.

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 triggering question, then capabilities, then conditional rules and category enumeration. No redundant sentences; every clause carries useful 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 an output schema present, the description focuses on what the schema cannot convey: when to call it, conditional inclusion of regional/international awards, result ordering, and the category vocabulary. Nothing needed for correct invocation 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 description coverage is already 100%, so parameter descriptions carry most of the load. The description still adds value by spelling out the allowed `category` list, clarifying the conditional effect of `prefecture` and `includeInternational`, and implying `openOnly` through the open-now concept. It does not cover `role` or `limit`, hence not a 5.

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?

The description states a specific verb and resource ('Returns advertising awards and their next entry period') and explicitly ties it to a user intent ('Use this when the user asks which advertising awards they can enter, or when entries open'). This distinguishes it from siblings like find_subsidies and list_ad_media without needing to open any schema.

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

Usage Guidelines5/5

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

It names the triggering user questions and gives explicit conditional rules: regional awards appear only with a matching prefecture and are listed first; international awards appear only when includeInternational is true. This is a rare case of when-to-use and behavioural conditions being spelled out completely.

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