Trillboards DOOH Advertising

register_device

WHEN TO USE:

Adding a new screen/kiosk/vending machine to the network
Updating device location or configuration
Re-registering a device after maintenance

RETURNS:

device_id: Your internal device ID (echoed back)
trillboards_device_id: Internal Trillboards device ID
fingerprint: Device fingerprint (e.g., "P_abc123")
embed_url: URL to load in the device's WebView
status: Device status

EXAMPLE: User: "Register a vending machine in NYC" register_device({ device_id: "vending-001-nyc", name: "NYC Office Lobby Vending", device_type: "vending_machine", location: { lat: 40.7128, lng: -74.0060, city: "New York", state: "NY", venue_type: "office" } })

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Human-readable device name
`specs`	No	Device specifications
`location`	No	Device location information
`metadata`	No	Additional custom metadata
`device_id`	Yes	Your internal unique device identifier
`device_type`	No	Type of device

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedAug 7, 2026
- addedInput schema / properties / device_id / description
```
Added value: +"Your internal unique device identifier"
```
- addedInput schema / properties / device_type / description
```
Added value: +"Type of device"
```
- addedInput schema / properties / location / description
```
Added value: +"Device location information"
```
- addedInput schema / properties / location / properties / address / description
```
Added value: +"Street address"
```
- addedInput schema / properties / location / properties / city / description
```
Added value: +"City"
```
- addedInput schema / properties / location / properties / country / description
```
Added value: +"Country"
```
- addedInput schema / properties / location / properties / lat / description
```
Added value: +"Latitude"
```
- addedInput schema / properties / location / properties / lng / description
```
Added value: +"Longitude"
```
- addedInput schema / properties / location / properties / state / description
```
Added value: +"State/province"
```
- addedInput schema / properties / location / properties / venue_type / description
```
Added value: +"Venue type (office, retail, gym, etc.)"
```
- addedInput schema / properties / location / properties / zip / description
```
Added value: +"Postal code"
```
- addedInput schema / properties / metadata / description
```
Added value: +"Additional custom metadata"
```
- addedInput schema / properties / name / description
```
Added value: +"Human-readable device name"
```
- addedInput schema / properties / specs / description
```
Added value: +"Device specifications"
```
- addedInput schema / properties / specs / properties / browser / description
```
Added value: +"Browser/WebView type"
```
- addedInput schema / properties / specs / properties / model / description
```
Added value: +"Device model"
```
- addedInput schema / properties / specs / properties / os / description
```
Added value: +"Operating system"
```
- addedInput schema / properties / specs / properties / screen_height / description
```
Added value: +"Screen height in pixels"
```
- addedInput schema / properties / specs / properties / screen_width / description
```
Added value: +"Screen width in pixels"
```
First observedMar 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the return payload (device_id, trillboards_device_id, fingerprint, embed_url, status) and gives a concrete example. While it doesn't detail side effects or auth requirements, the upsert nature is implied by 'register or update'.

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?

The description is well-organized with clear sections (main purpose, WHEN TO USE, RETURNS, EXAMPLE). Each section earns its place, with no redundant content. It's appropriately sized for the tool's complexity.

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?

Given the tool's nested objects (specs, location) and missing output schema, the description compensates by listing all return fields and showing a complete example. It doesn't cover error handling, but the essential usage context is thorough.

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 baseline is 3. The description adds an example with device_id, name, device_type, and location, demonstrating real-world usage, but the schema already fully explains each parameter. No significant extra semantic info.

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 opens with 'Register or update a device in the partner's network', clearly stating the verb (register/update) and resource (device). It distinguishes from siblings like delete_device, get_device, and list_devices by covering both creation and modification scenarios.

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?

Explicit 'WHEN TO USE' section lists three concrete scenarios: adding a new screen/kiosk/vending machine, updating device info, and re-registering after maintenance. It lacks explicit when-not-to-use or alternatives, but the use cases are clear enough.

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 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?