Skip to main content
Glama
Sign In

GenFlick

by com.genflick
OverviewDiscussionsAdmin

Organize documents

native.organize_identity_documents
DestructiveIdempotent

Read the document directory, move or archive an exact document, restore it, rename/move a folder, or delete an explicitly requested item. Read the current revision first. Preview folder deletion and preserve its exact returned plan; deleting contents must be requested explicitly.

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": {
      "work_id": "<work_id>",
      "arguments": "<arguments>",
      "expected_catalog_version": "<expected_catalog_version>",
      "read_skills": "<read_skills>",
      "request_key": "<request_key>"
    },
    "name": "native.organize_identity_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
work_idYes
argumentsYes
read_skillsYesExact required native skills and their dependencies, copied from the accepted session bootstrap's skills array. Include only entries in that array. General mcp.* guides and native.{studio}.instructions are guidance, not native skill proofs.
request_keyYes
publication_proposal_idNoFor native Social scheduling, the exact server-approved publication proposal. This identifier cannot confer approval by itself.
expected_catalog_versionYesFor a new session, read a studios/{studio}/native/{pack} child toolset and copy invocation.catalog_version from a native tool descriptor. Do not use the top-level library version. For calls in an existing session, use that session proposal's catalog_version.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=true, yet the description still adds meaningful behavior: folder deletion must be previewed and the returned plan preserved, and deleting contents requires an explicit flag. That is exactly the extra context the annotations cannot express. It omits conflict/version-mismatch behavior and what happens when the revision is stale.

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?

Three sentences, front-loaded with the operation inventory, followed by the preconditions and the deletion protocol. Nearly every clause carries information, though the fragmented comma-list style makes the operation-to-parameter mapping slightly harder to parse than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is not required, but for a 6-parameter, 10-operation tool with nested objects and destructive scope the description is thin on how to obtain the current revision and what to do on a revision mismatch. It is adequate for safe deletion but incomplete for the move/rename/reorder paths.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%, and the description adds meaning to the operation enum by framing move/archive/restore of a single document versus rename/move of a folder, plus the revision precondition implied by expected_revision and the deletion_plan/delete_contents pairing. It says nothing about work_id, request_key, read_skills, expected_catalog_version, or operation_id reuse, so half the parameters remain unexplained outside the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names concrete verbs and resources: read the document directory, move/archive/restore an exact document, rename or move a folder, delete an explicitly requested item, and preview a folder deletion. That is specific enough for an agent to know the domain, but it bundles many operations into one tool and never distinguishes itself from close siblings such as native.move_document, native.move_documents, or native.create_document_folder.

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?

It gives real procedural guidance for the destructive path: read the current revision first, preview folder deletion, preserve the exact returned plan, and require explicit request to delete contents. However, it gives no guidance on when to choose this tool over the many overlapping document/move siblings, so routing between alternatives 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.

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