Skip to main content
Glama

Visibility Genies

List archived projects

list_archived_projects
Read-only

Lists archived projects visible to this connection, with their id, name, domain and organizationId. Free: buys no data. Pass an id as archivedProjectId to restore_project. A project with deleting=true is being permanently deleted and cannot be restored. Does not include active projects; use list_projects for those.

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": "list_archived_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
projectsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description goes further by disclosing the free-tier behavior ("Free: buys no data") and the irreversibility of projects flagged deleting=true. These are operational facts an agent cannot derive from the schema or annotations.

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 purpose, then routing, then the caveat — good ordering with no filler. Minor redundancy: listing id/name/domain/organizationId duplicates what the output schema already declares, and "Free: buys no data" is terse to the point of ambiguity.

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 zero-parameter read tool with a full output schema and read-only annotations, this covers everything remaining: scope, sibling boundary, restoration pathway, and the deletion caveat. An agent can select and call it correctly without further context.

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?

The tool takes zero parameters, so the baseline is 4. The description adds useful cross-tool meaning by explaining where the returned id is consumed (archivedProjectId on restore_project), which is more than the empty schema conveys.

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 ("Lists archived projects visible to this connection") and immediately enumerates the returned fields, so the agent knows exactly what it gets. It also explicitly distinguishes itself from the sibling: "Does not include active projects; use list_projects for those."

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 routing in both directions: use list_projects for active projects, and pass the returned id as archivedProjectId to restore_project. It also flags the exclusion case (deleting=true cannot be restored), which changes what the agent should do next.

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