Skip to main content
Glama

save_sop

Create (without sop_id) or update (with sop_id) a SOP of the user's organization. Owners/admins only. steps = ordered list of {title, body?, role?} (max 40). outpost_ids = the outposts it applies to (from list_clients; omit = all). status=archived archives it, status=active restores it. Max 10 active SOP: the 11th is refused with limit_reached. Show the user the title and steps before saving.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_sop"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsNoPassaggi della procedura: array di stringhe in ordine.
titleNoTitolo della procedura (testo breve).
sop_idNoOmit to create a new SOP.
sourceNoWhere it comes from, e.g. "crm:sop#30".
statusNoactive oppure archived.
scheduleNoFree text, e.g. "daily 08:30" or "Monday".
confirm_idNoToken di conferma ritornato dall'anteprima. Ripassa lo STESSO payload + confirm_id per eseguire davvero la scrittura.
descriptionNoDescrizione breve in testo semplice.
outpost_idsNoElenco di id outpost (seller × marketplace), array di stringhe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / description / description
      Added value: +"Descrizione breve in testo semplice."
    • addedInput schema / properties / outpost_ids / description
      Added value: +"Elenco di id outpost (seller × marketplace), array di stringhe."
    • addedInput schema / properties / status / description
      Added value: +"active oppure archived."
    • addedInput schema / properties / steps / description
      Added value: +"Passaggi della procedura: array di stringhe in ordine."
    • addedInput schema / properties / steps / items / properties / body / description
      Added value: +"Testo completo (Markdown)."
    • addedInput schema / properties / steps / items / properties / role / description
      Added value: +"Ruolo a cui è destinata la procedura, es. ads, listing, operations."
    • addedInput schema / properties / steps / items / properties / title / description
      Added value: +"Titolo della procedura (testo breve)."
    • addedInput schema / properties / title / description
      Added value: +"Titolo della procedura (testo breve)."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the annotations (which only say non-read-only, non-destructive, closed-world) by disclosing permission requirements, a hard cap of 10 active SOPs with the exact failure 'limit_reached' on the 11th, the max-40 step limit, and that status=archived/active archives or restores. It also prescribes a user-confirmation step before writing, which is meaningful safety context an agent would not otherwise have.

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 create/update distinction and free of filler; every clause carries a constraint. The single dense paragraph packs many independent rules together, so it is efficient but slightly harder to scan than a structured list would be.

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 9-parameter mutation tool with no output schema, the description covers modes, permissions, quotas, ordering of steps, outpost scoping and archive behavior, which is nearly everything needed. The gap is update behavior for existing steps and what the response contains after a save.

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 meaning: the steps element shape and 40-item cap, that omitting outpost_ids means 'all', that omitting sop_id means create, and the archive/restore effect of status. It does not clarify update semantics (whether steps replace or merge), which is the remaining ambiguity.

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?

Opens with a specific verb plus resource and splits the two modes explicitly: 'Create (without sop_id) or update (with sop_id) a SOP'. That mode split is the key differentiator against the read-side sibling get_sop, so an agent can select it 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 Guidelines4/5

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

Gives concrete preconditions and constraints: 'Owners/admins only', 'Show the user the title and steps before saving', and outpost_ids sourced 'from list_clients'. It stops short of naming the read alternative (get_sop) for inspection, so the when-not guidance is implicit rather than explicit.

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