Skip to main content
Glama
Sign In

Taskriz

by com.taskriz
OverviewDiscussionsAdmin

Set the Agent’s Branding

set_branding
DestructiveIdempotent

How people know which brand this Agent's requests are from: a LOGO (shown in place of its initials wherever the Agent appears) and a FOOTER (drawn by Taskriz at the end of each request). Fixed per Agent. Each is set on its own — omit one to leave it; null removes it. For a logo, ask the person for the image (a square PNG, JPEG or WebP, at least 128 × 128, up to 1 MB), upload it with create_attachment, then pass its attachment_id. Taskriz re-encodes it and answers it here so you can see it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>"
    },
    "name": "set_branding"
  }
}

Input Schema

NameRequiredDescriptionDefault
footerNoThe footer (null removes it).
agent_idYesThe Agent (from list_agents or create_agent).
logo_attachment_idNoThe logo, uploaded with create_attachment (null removes the logo).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description explains that values are fixed per Agent, that omission preserves and null deletes the existing logo/footer, and that Taskriz re-encodes the image and echoes it back in the response so the agent can verify it. That covers what is mutated, what is destroyed, and what comes back.

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?

Information-dense with no filler: concept definition, per-field semantics, removal behavior, then the logo workflow. The opening clause 'How people know which brand this Agent's requests are from' is slightly indirect but earns its place as framing rather than repetition.

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?

For a 3-parameter mutation tool with no output schema, the description supplies prerequisites, validation constraints, update/removal semantics, and a hint about the response. The only soft spot is that the returned representation is described only as 'answers it here so you can see it' rather than its shape.

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 would be 3, but the description adds meaning the schema lacks: the logo's accepted formats and size floor/ceiling (square PNG/JPEG/WebP, ≥128×128, ≤1 MB) and the fact that the footer is rendered by Taskriz at the end of each request. The omit-versus-null distinction is also clarified in prose.

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 names the concrete resources being set (a LOGO shown in place of initials, a FOOTER appended by Taskriz to each request) and scopes them as 'Fixed per Agent'. That is a specific verb+resource pair an agent can distinguish from siblings like create_attachment or set_catalog without opening the schema.

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 gives real operational guidance: each field is set independently, 'omit one to leave it; null removes it', and a logo requires first asking the person for an image, uploading it with create_attachment, then passing the attachment_id. It does not state explicit when-not-to-use conditions, but the prerequisite chain and partial-update semantics are clearly spelled out.

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

All Taskriz 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