Skip to main content
Glama

Visibility Genies

Archive a project

archive_project
Destructive

Archives an active project, keeping its saved data so restore_project can bring it back. Free: buys no data. Use a projectId from list_projects. The workspace's only active project cannot be archived. This does not permanently delete anything.

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": {
      "projectId": "<projectId>"
    },
    "name": "archive_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
successYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, so mutability is already known; the description adds the crucial nuance that data is retained and recovery via restore_project is possible, and that nothing is permanently deleted, along with the single-active-project restriction. This meaningfully softens and clarifies what the destructive flag implies. The one weak spot is the cryptic fragment "Free: buys no data," which does not clearly convey what resource or quota is affected.

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 core action and tightly written across four short sentences, each carrying a distinct fact (reversibility, ID source, constraint, non-destructiveness). The phrase "Free: buys no data" is confusing and costs it a perfect score.

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 one-parameter mutation tool with full schema coverage, annotations and an output schema, the description covers the essentials an agent needs: what it does, where the ID comes from, the blocking constraint, and reversibility. Return values need not be explained since an output schema exists.

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 100% and the single projectId parameter is fully documented there, including the pointer to list_projects. The description repeats the same list_projects hint but adds no new format, ID-source, or validation detail, so baseline 3 applies.

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 ("Archives an active project") plus the key scope (active projects), and explicitly contrasts with restore_project. An agent can distinguish it from siblings like restore_project or create_project without opening any 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 prerequisites and constraints: "Use a projectId from list_projects" and "The workspace's only active project cannot be archived," and names restore_project as the undo path. It stops short of stating when an agent should prefer archiving over other lifecycle actions in a general sense, but the object-level guidance is clear.

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