Skip to main content
Glama

List Cuttr skills

list_skills
Read-only

Every editor in Cuttr AI Video Editing: slug, name, what it makes, what it needs, and whether this member has it unlocked.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the response is scoped per member, including whether 'this member has it unlocked', which hints at personalization. It says nothing about result size, ordering, or whether skills can be filtered.

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?

A single compact sentence with the resource front-loaded and the returned fields trailing as a list — nothing wasted. The telegraphic phrasing ('what it makes, what it needs') is efficient but slightly informal for a schema-adjacent definition.

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 parameters, no output schema, and a read-only annotation, the description covers what is needed by describing the contents of each returned item. It stops short of saying whether this is the right entry point before get_skill, which is the one gap for a discovery tool.

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; there is no argument semantics for the description to explain. The description instead spends its words on the response shape, which is the only meaningful semantic content available.

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 the resource (every editor/skill in Cuttr AI Video Editing) and enumerates the fields returned, so an agent can tell it is a bulk catalog read rather than a single-skill lookup like get_skill. The listing verb is only implied by 'Every editor...' rather than stated, which slightly softens an otherwise clear purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no prerequisites, and no named alternative such as get_skill for fetching one skill's details. An agent must infer from the name and field list that this is the browse-first call, which is a reasonable inference but not stated.

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