Skip to main content
Glama
Sign In

ChatCut

by io.chatcut
OverviewDiscussionsAdmin

list_projects

Read-onlyIdempotent

List accessible projects, most recently updated first, to find earlier work. Pass a returned projectId to read_chat_history, read_project, browse_assets and inspect_asset to see what was said and used.

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_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum projects to return. Defaults to 20; maximum 100.
queryNoCase-insensitive literal substring of the project name or description.
editorBaseUrlNoEditor origin/base URL for the returned URLs. Defaults to CHATCUT_EDITOR_URL or http://localhost:5173.
includeDeletedNoAlso list soft-deleted projects (marked with deletionState) so they can be restored with restore_project. Defaults to false.
installationReceiptNoOnly when the hosted plugin's installation guide left a pending local installation receipt: pass its code unchanged to connect that installation with its landing-page entry. Never invent a code. Omit for ordinary project discovery and ChatCut Desktop. Invalid values are ignored, and a pending acknowledgment never prevents project use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 20,
+  "description": "Maximum projects to return. Defaults to 20; maximum 100.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Case-insensitive literal substring of the project name or description.",
+  "maxLength": 200,
+  "type": "string"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and closed-world scope, so the safety profile is covered. The description adds ordering semantics and the downstream chaining behavior, which the annotations do not convey. It stops short of describing result shape or how soft-deleted entries appear, but that is partly handled in the schema.

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?

Two sentences, both earning their place: the first establishes scope and ordering, the second establishes the follow-on workflow. Purpose is front-loaded with zero filler.

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?

With no output schema and five parameters, the description covers the essentials: what is listed, how it is ordered, and what to do with the returned projectId. It could say more about what each project record contains, but the chaining hint largely compensates for the missing output schema.

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%, including limit bounds, the literal substring matching of query, editorBaseUrl defaults, includeDeleted behavior, and the installationReceipt caveat. The description adds nothing parameter-specific beyond the notion that projectId values come back from this call, 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?

The description opens with a specific verb and resource ("List accessible projects"), states the ordering ("most recently updated first"), and gives the intent ("to find earlier work"). This clearly separates it from siblings like create_project, delete_project, or read_project.

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?

It gives a concrete workflow: use this to find earlier work, then pass a returned projectId into read_chat_history, read_project, browse_assets, and inspect_asset. That is strong positive guidance, but it never states when not to use it (e.g., versus a targeted lookup or create_project for new work).

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

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