Field Service Business Platform by Doing Work

shops_setBrand

Set how this shop's quotes, invoices and emails to customers look, on the customer's page, in the PDF and in every email (owner only). The owner can also change it on the brand page at /p/shop/brand. Send only what changes; null clears a field. accent_color is "#rrggbb" and must reach 4.5 to 1 contrast on white (the default is #1f4fd1). logo_base64 is a PNG or JPEG of up to 5 MB, stored as a JPEG of at most 600 pixels on its long side. sent_with_doing_work (on by default) prints "Sent with Doing Work" in the PDF footer, on the page and at the bottom of emails.

Input Schema

Name	Required	Description
`footer`	No	Up to 300 characters printed at the bottom, such as payment terms or a thank you.
`shop_id`	Yes
`logo_base64`	No	A PNG or JPEG file, base64. null removes the logo.
`accent_color`	No	"#rrggbb", dark enough to read on white. null goes back to the default.
`license_number`	No	Up to 80 characters, printed as "License ...".
`sent_with_doing_work`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description discloses critical behavioral constraints not in the schema, such as the required contrast ratio for accent_color (4.5 to 1), file size/format for logo_base64, and default behaviors for sent_with_doing_work. This is excellent operational detail.

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 definition is dense but highly effective. It front-loads the purpose before detailing technical constraints, allowing the agent to quickly identify if the tool is relevant, even if it doesn't fully read the operational specifics.

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?

Despite being a complex, multi-modal configuration tool (color, file upload, text rendering across PDFs/Emails), the description is complete. It covers permissions, update logic, and technical input requirements, providing all necessary information for a successful 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?

While the schema defines types, the description adds vital operational meaning to the parameters, specifically detailing logo storage format (JPEG conversion) and the specific nature of color encoding ('#rrggbb'). This compensates well for the 67% coverage.

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 clearly defines the scope as setting the brand appearance for quotes, invoices, and emails for a shop. It also clarifies the user permission requirement (owner only), making it distinct from general shop settings.

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?

It provides strong guidance on partial updates by stating 'Send only what changes; null clears a field.' It also explicitly mentions the user alternative on the brand page, helping the agent decide between automated and manual configuration.

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

All Field Service Business Platform by Doing Work 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?