Skip to main content
Glama

Refine Event Cover

refine_event_cover

Refine the event's CURRENT cover with a short instruction ('make it warmer', 'swap the background', 'bigger title') — we re-render from the existing cover, keep the composition, and set the new one. Do not add event times unless the host explicitly asks for them on the flyer. There must already be a cover (generate_event_cover first). Counts against the monthly AI-image limit. Works on a live event you host (event_id) OR an unclaimed draft (draft_id + edit_token), so a draft's picture can be iterated before publishing. Needs a connected account.

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": {
      "instruction": "<instruction>"
    },
    "name": "refine_event_cover"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idNo
event_idNo
edit_tokenNo
instructionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / draft_id
      Added value: +{
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / edit_token
      Added value: +{
      +  "maxLength": 256,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "event_id",
      -  "instruction"
      -]New value: +[
      +  "instruction"
      +]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing billing ("Counts against the monthly AI-image limit"), an auth precondition ("Needs a connected account"), and the fact that composition is preserved. The only mild gap is that it never says the previous cover is overwritten rather than kept as a version, which matters when destructiveHint is false.

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?

Front-loaded with the core action, then prerequisites, then billing, then the two ID modes. Dense but efficient; the em-dash asides and parentheticals add mild clutter without obscuring the key routing information.

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 4-parameter mutation tool with no output schema and no schema descriptions, the description covers action, prerequisites, auth, cost, and both invocation modes. Only the return value and whether the prior cover is retained are left unstated, both low-risk given the refinement framing.

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 description coverage is 0%, so the description must carry all parameter meaning and largely does: `instruction` is scoped to a short natural-language edit with three concrete examples, and the event_id versus draft_id + edit_token pairing is mapped to its two use cases. Minor gap: `edit_token`'s provenance (where the caller obtains it) is never stated.

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?

Names a specific verb and resource ("refine the event's CURRENT cover") and immediately explains the mechanism: re-render from the existing cover, preserve composition, set the new one. This cleanly separates it from generate_event_cover, which by implication creates a cover from scratch.

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?

States prerequisites explicitly ("There must already be a cover (generate_event_cover first)"), names the alternative for the other case, and gives an exclusion rule ("Do not add event times unless the host explicitly asks"). It also distinguishes the two operating modes: live event via event_id versus unclaimed draft via draft_id + edit_token.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.