Skip to main content
Glama

Plunder & Riffle Meme Engine

Save the brand voice

save_brand_default

Save a researched brandProfile as this key's default voice (later calls use it unless they pass their own; a pinned bot still wins). {} clears. Free. Write scope.

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": {
      "brandProfile": "<brandProfile>"
    },
    "name": "save_brand_default"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandProfileYesThe research_brand output, unchanged (name + voice required). {} clears.

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?

Annotations only supply destructiveHint=false, so the description carries the burden and does so well: it discloses the cost ('Free'), the auth requirement ('Write scope'), overwrite/precedence semantics, and that `{}` clears the default — behavior an agent cannot get from the annotation or the schema.

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?

A single dense sentence plus two short fragments; every clause carries a distinct fact (what is saved, precedence, clearing, cost, scope) with the core action front-loaded. Nothing is redundant.

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?

For a one-parameter mutation with no output schema and a thin annotation set, the description supplies everything an agent needs to call it correctly: input provenance and shape, overwrite/clear behavior, precedence, cost, and permission scope.

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% and the nested object already documents its fields, so the baseline is 3. The description adds real meaning beyond that: the object must be passed 'unchanged' as `research_brand` output, and `{}` is the sentinel for clearing, which the schema states but the description reinforces with intent.

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: save a researched `brandProfile` as this key's default voice. It also names the source of the input (`research_brand` output), so an agent can distinguish this from `get_brand_default` or the `research_brand` producer without inspecting schemas.

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

Usage Guidelines3/5

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

Usage is implied through the workflow — the profile must come from `research_brand` — and the precedence rules (later calls use it unless they pass their own; a pinned bot still wins) clarify when the saved value takes effect. However, no sibling is named as an alternative, and the obvious 'call get_brand_default to inspect the current default first' case is left to inference.

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.

Resources