Skip to main content
Glama

Trillboards DOOH Advertising

by io.github.snehdhruv
OverviewDiscussionsAdmin

get_adcp_capabilities

[AdCP] Get the seller agent's AdCP capabilities and supported protocols.

Returns the full capability declaration for this AdCP DOOH seller agent. This tool does NOT require authentication.

WHEN TO USE:

  • Discovering what protocols the seller agent supports (Signals, Media Buy)

  • Understanding available audience signals and data methodology

  • Getting MCP endpoint and discovery URLs

RETURNS:

  • supported_protocols: ['signals', 'media_buy']

  • inventory: DOOH format details, network size

  • audience_data: signal list, methodology, refresh rate

  • pricing: model, currency, floor CPM

  • discovery: well_known_url, mcp_endpoint

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
    • removedInput schema / properties / context
      Removed value: -{
-  "additionalProperties": {},
-  "type": "object"
-}
  2. Changed3 schema fields changed
    • removedInput schema / properties / adcp_major_version
      Removed value: -{
-  "description": "Legacy major-precision AdCP version pin, an integer (e.g. 3), carried since 3.0. Prefer adcp_version. A major this agent does not speak is answered with a VERSION_UNSUPPORTED task failure; get_adcp_capabilities.adcp.major_versions lists the supported set.",
-  "type": "integer"
-}
    • removedInput schema / properties / adcp_version
      Removed value: -{
-  "description": "Release-precision AdCP version this request is pinned to, \"MAJOR.RELEASE\" (e.g. \"3.1\"). A release this agent does not speak is answered with a VERSION_UNSUPPORTED task failure listing the ones it does. Read get_adcp_capabilities.adcp.supported_versions to pin correctly.",
-  "type": "string"
-}
    • removedInput schema / properties / context / description
      Removed value: -"Opaque caller-supplied correlation object. Echoed back byte-for-byte, unparsed, on both successful and failed responses; the agent never reads its contents."
  3. Changed3 schema fields changed
    • addedInput schema / properties / adcp_major_version
      Added value: +{
+  "description": "Legacy major-precision AdCP version pin, an integer (e.g. 3), carried since 3.0. Prefer adcp_version. A major this agent does not speak is answered with a VERSION_UNSUPPORTED task failure; get_adcp_capabilities.adcp.major_versions lists the supported set.",
+  "type": "integer"
+}
    • addedInput schema / properties / adcp_version
      Added value: +{
+  "description": "Release-precision AdCP version this request is pinned to, \"MAJOR.RELEASE\" (e.g. \"3.1\"). A release this agent does not speak is answered with a VERSION_UNSUPPORTED task failure listing the ones it does. Read get_adcp_capabilities.adcp.supported_versions to pin correctly.",
+  "type": "string"
+}
    • addedInput schema / properties / context / description
      Added value: +"Opaque caller-supplied correlation object. Echoed back byte-for-byte, unparsed, on both successful and failed responses; the agent never reads its contents."
  4. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
+  "additionalProperties": {},
+  "type": "object"
+}
  5. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden. It explicitly states 'This tool does NOT require authentication' and outlines the return structure. It does not mention caching, volatility, or error behavior, but for a read-only capability declaration this is reasonably transparent and not misleading.

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 description is well-structured with separate WHEN TO USE and RETURNS sections, making it easy to scan. It is not overly long, though the opening sentence and the following 'Returns the full capability declaration' line are slightly redundant.

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?

For a zero-parameter tool with no output schema, the description fully covers what an agent needs: when to use it, authentication status, and a detailed breakdown of the returned capability fields. Nothing essential is missing for correct invocation.

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?

The input schema has zero parameters and 100% schema coverage, so there are no parameters to document. The baseline for a zero-parameter tool is 4, and the description appropriately signals that no inputs or authentication are required.

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?

Clearly specifies the tool retrieves the seller agent's AdCP capabilities and supported protocols, and goes on to enumerate the major return categories (protocols, inventory, audience_data, pricing, discovery). This distinguishes it from sibling tools like get_partner_info, discover_inventory, or describe_endpoint, so an agent can select it without ambiguity.

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?

Provides an explicit 'WHEN TO USE' section listing three concrete use cases: discovering supported protocols, understanding audience signals, and getting MCP endpoint/discovery URLs. It lacks explicit when-not-to-use guidance or named alternatives, so it does not fully reach the top score.

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

All Trillboards DOOH Advertising toolsInspect
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