Skip to main content
Glama

legal_put_social

Switch social networks and set their plain HTTPS profile URLs, then rewrite the Datenschutz social-media section; send the full desired network set because omitted networks are switched off.

Instructions

Switch social networks and set their profile URLs (plain https only), then rewrite the Datenschutz social-media section; with nothing on, the section is removed. NOT a merge: every network missing from networks is switched off, so always send the full set you want on. Needs the modules imported and a Datenschutz document (409 otherwise). Returns the new state as legal_get_social does. Requires cvrt-legal 0.6.0+.

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": {
      "site": "<site>",
      "networks": "<networks>"
    },
    "name": "legal_put_social"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
networksYesnetwork key (as legal_get_social lists under available) => { enabled, urls }

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.14.0
    • addedInput schema / properties / networks / additionalProperties / properties / enabled / description
      Added value: +"Network on/off; on needs at least one URL"
    • addedInput schema / properties / networks / additionalProperties / properties / urls / description
      Added value: +"Profile URLs, plain https; blanks are dropped"
    • changedInput schema / properties / networks / description
      Previous value: -"network key => { enabled, urls }"New value: +"network key (as legal_get_social lists under available) => { enabled, urls }"
  2. Addedv3.4.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses destructive replace semantics, that the section is removed when nothing is enabled, the 409 failure mode, URL format restriction, and the return shape. An agent can predict the outcome of the call before making it.

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?

Dense but front-loaded: action and side effect first, then the replace-semantics warning, then prerequisites and version. Semicolon-separated clauses carry distinct facts with no filler sentences.

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 nested-object mutation tool with no annotations and no output schema, the definition covers prerequisites, error behavior, overwrite semantics, URL constraints, version requirement, and return value. Nothing an agent needs to call it 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% and already documents site, enabled, and urls, so the schema does the heavy lifting. The description still adds decisive meaning beyond it: that networks must be the complete desired set rather than a partial patch, which changes how the parameter must be built.

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 (switch social networks, set profile URLs) and the side effect (rewrite the Datenschutz social-media section). It is clearly distinguished from the read sibling by noting it 'Returns the new state as legal_get_social does', so an agent knows which of the pair mutates.

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?

Gives explicit when-to-use constraints: it is NOT a merge, missing networks are switched off, so the full set must always be sent. It also names prerequisites (modules imported, Datenschutz document present, otherwise 409) and a version floor, leaving nothing about applicability to inference.

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

Deploy Server

Other Tools