Skip to main content
Glama

Content Sweep

by ai.contentsweep
OverviewDiscussionsAdmin

delegate_authority

Record the rights holder's existing authority for exact works and actions with a reference, attestation version and future expiry. Requires rights scope and rights_authorized=true. Returns a delegation id for create_quote. Set can_appoint_content_sweep=true only when the mandate permits appointment; submission requires it. Delegation can be revoked immediately; payment never substitutes for authority.

Input Schema

NameRequiredDescriptionDefault
bodyYesTenant rights_holder_id, work_ids, allowed actions, rights_authorized=true, appointment permission, authorization_reference, attestation_version and future expires_at. Current attestation version is published at /api/v1/capabilities.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / body / additionalProperties
      Previous value: -trueNew value: +false
    • addedInput schema / properties / body / description
      Added value: +"Tenant rights_holder_id, work_ids, allowed actions, rights_authorized=true, appointment permission, authorization_reference, attestation_version and future expires_at. Current attestation version is published at /api/v1/capabilities."
    • addedInput schema / properties / body / properties
      Added value: +{
+  "actions": {
+    "items": {
+      "enum": [
+        "search",
+        "investigate",
+        "evidence",
+        "prepare",
+        "submit",
+        "status",
+        "monitor"
+      ],
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  "attestation_version": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "authorization_reference": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "can_appoint_content_sweep": {
+    "type": "boolean"
+  },
+  "expires_at": {
+    "format": "date-time",
+    "type": "string"
+  },
+  "rights_authorized": {
+    "const": true
+  },
+  "rights_holder_id": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "work_ids": {
+    "items": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "maxItems": 100,
+    "minItems": 1,
+    "type": "array"
+  }
+}
    • addedInput schema / properties / body / required
      Added value: +[
+  "rights_holder_id",
+  "work_ids",
+  "actions",
+  "rights_authorized",
+  "can_appoint_content_sweep",
+  "authorization_reference",
+  "attestation_version",
+  "expires_at"
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=true), and the description adds behavior annotations don't carry: immediate revocability, future expiry semantics, the attestation version source, and the 'payment never substitutes for authority' guardrail. The only missing piece is what happens on re-delegation or conflict.

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?

Four tightly packed sentences, front-loaded with the core action and ending with the key constraint (payment ≠ authority). No filler, though the density makes it read more like a spec than prose.

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?

There is no output schema, and the description compensates by stating the return ('a delegation id for create_quote'). Preconditions, conditional flags, revocation, and expiry are all covered; only error/duplicate-handling behavior is absent for a non-idempotent mutation.

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 body is self-documented, but the description still adds meaning the schema cannot: the conditional intent behind can_appoint_content_sweep ('only when the mandate permits appointment; submission requires it') and the role of the authorization_reference/attestation_version pair. This is more than a restatement of field names.

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?

Specific verb+resource: 'Record the rights holder's existing authority for exact works and actions' with the qualifying artifacts (reference, attestation version, expiry). It implicitly separates itself from revoke_authority by noting revocation is possible and names create_quote as the downstream consumer, so an agent can place it in the workflow.

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 ('Requires rights scope and rights_authorized=true') and a conditional rule for can_appoint_content_sweep tied to whether submission is needed. It stops short of naming the alternative tool (revoke_authority) or stating when not to delegate, so it is clear context without explicit exclusions.

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

All Content Sweep 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