dexe-mcp

Generate a deterministic placeholder avatar for a DAO

dexe_dao_generate_avatar

Generates a deterministic DAO avatar JPEG from the DAO name's initials and a hash-colored gradient, pins it to remote storage, and returns its CID, filename, and URL.

Instructions

Writes to a remote service. Renders a real JPEG of the DAO's initials over a hash-coloured gradient and pins it, returning {avatarCID, avatarFileName, avatarUrl}. Deterministic.

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": {
      "daoName": "<daoName>"
    },
    "name": "dexe_dao_generate_avatar"
  }
}

Input Schema

Name	Required	Description	Default
`size`	No	Output image size in px (square).
`daoName`	Yes	DAO name; first 1–2 alphanumeric chars become the avatar initials.

Output Schema

Name	Required	Description	Default
`size`	Yes
`pinnedAt`	Yes
`avatarCID`	Yes
`avatarUrl`	Yes
`avatarFileName`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.37.1Nov 11, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description's contribution is the important extra: it writes to a remote service and pins the resulting asset, which tells the agent this has a persistent external side effect. The 'Deterministic' note usefully implies repeat calls produce the same image. It does not say which backing service is written to or whether pinning can be undone.

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?

Three short sentences plus a fragment, front-loaded with the side-effect warning. Nothing is wasted, though the trailing 'Deterministic.' reads as an afterthought rather than a structured statement.

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?

With annotations, a full output schema, and complete schema descriptions, this definition covers what the tool does and returns. The remaining gap is the identity of the remote service and any failure or overwrite behavior when the same DAO avatar is pinned twice.

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 both parameters are already documented in the schema and a baseline of 3 applies. The description reinforces how daoName drives the initials and that output is a square image, but adds no format detail for size beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses specific verbs and resources: it 'renders a real JPEG of the DAO's initials over a hash-coloured gradient and pins it.' That is far more informative than the title alone and implicitly separates it from dexe_ipfs_upload_avatar. It stops short of explicitly naming a sibling or stating the boundary, so it lands at 4 rather than 5.

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

Usage Guidelines2/5

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

The description explains what happens during the call but never says when to choose this tool instead of dexe_ipfs_upload_avatar or dexe_ipfs_upload_file. The word 'Writes' signals a side effect, but there are no prerequisites, exclusions, or alternative conditions given.

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

Deploy Server