Convocore

update_agent_custom_css

Destructive

Overwrite the agent's customCSS field with new CSS that styles the chat widget. IMPORTANT: this REPLACES the existing customCSS value — always pass the FULL merged CSS (existing + your new rules), not just the delta. Workflow: (1) call get_widget_css_styling_guide to load selectors + rules, (2) optionally call get_agent_custom_css to read what's already there, (3) generate the merged CSS following the guide, (4) call this tool to persist. Pass an empty string to clear all customCSS for the agent.

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": {
      "agentId": "<agentId>",
      "customCSS": "<customCSS>"
    },
    "name": "update_agent_custom_css"
  }
}

Input Schema

Name	Required	Description	Default
`agentId`	Yes	The agent ID whose customCSS field you want to overwrite
`customCSS`	Yes	The full CSS to write to the agent.customCSS field. REPLACES the existing value entirely. Use an empty string to clear.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description adds the crucial non-obvious behavior: the field is replaced wholesale, so a partial delta silently destroys prior rules. That is exactly the destructive consequence an agent must know before calling, plus the clearing semantics.

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?

Front-loaded with the action, then the destructive warning, then a numbered workflow, then the clearing case. No filler sentences; the emphasis on REPLACES is warranted for a destructive tool and every clause carries a decision-relevant fact.

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?

Two required parameters, no output schema to explain, and the description covers prerequisites, merge semantics, and clearing behavior. Nothing an agent needs to invoke this correctly is missing.

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 is 3, but the description adds real semantic weight by insisting customCSS be the FULL merged value rather than a delta — a constraint the schema field text only states briefly. agentId gets no additional treatment beyond the schema, keeping it just short of a 5.

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?

States a specific verb and resource ('Overwrite the agent's customCSS field') plus the domain purpose ('styles the chat widget'), which clearly separates it from get_agent_custom_css (read) and update_agent (general agent mutation). An agent can pick this 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 Guidelines5/5

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

Provides an explicit ordered workflow naming the prerequisite sibling (get_widget_css_styling_guide), the optional read (get_agent_custom_css), and the terminal write. It also gives the clear-case escape hatch: empty string clears all customCSS.

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

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