Skip to main content
Glama
Sign In

Howseen

by ai.howseen
OverviewDiscussionsAdmin

Update the writing instructions

update_brand_instructions
DestructiveIdempotent

Change the brand's writing instructions (Settings > Writing rules): the client's own rules every article must follow (tone, words to avoid, competitors never to name, facts to state...). Binding on every writing path from now on; an article breaking one is held, never published. mode "append" adds a rule, "replace" (default) sets the whole text (max 2000 characters, never cut). Read get_brand_settings first. Preview first; confirm: true saves.

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": {
      "instructions": "<instructions>"
    },
    "name": "update_brand_instructions"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoreplace (default) or append.
brandNoBrand id, name or domain (from list_brands). Optional when the account has a single brand.
confirmNoLeave out (or false) to get a preview: nothing changes. Set true ONLY after the user approved that exact preview.
instructionsYesThe instructions text (replace) or the rule to add (append). Empty with replace clears them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior1/5

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

The annotations declare idempotentHint=true, but the description says mode "append" adds a rule. Repeating an append call with the same arguments would likely add the rule again, so the description contradicts the idempotency annotation in an operationally important way for retries. The description otherwise adds useful context about destructive replacement, binding effects, and preview confirmation.

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?

The description is dense and front-loaded, with no wasted sentences. It could be slightly easier to scan if the mode and confirm workflow were separated from the long parenthetical rule examples, but it remains appropriately sized for a destructive settings mutation.

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?

Given no output schema but rich annotations and a fully described schema, the description covers the critical missing context: prerequisites, preview/confirm behavior, mode semantics, character limits, and the downstream consequence of invalid rules. An agent has enough information to avoid accidental writes.

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 100%, so the schema already documents all four parameters, including brand and confirm. The description adds useful meaning beyond the schema for mode default behavior, append-vs-replace semantics, the 2000-character limit, and the preview/confirm workflow, but it does not mention the optional brand parameter.

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 states a specific verb and resource: changing the brand's writing instructions, with concrete examples of what those rules govern. It distinguishes the tool from get_brand_settings by explicitly saying to read settings first, and from unrelated siblings by scoping the change to writing rules.

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?

It gives an explicit prerequisite (read get_brand_settings first), a workflow (preview first; confirm: true saves), and mode selection guidance: append adds a rule, replace sets the whole text. This is enough for an agent to choose the tool and invoke it correctly.

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

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