Skip to main content
Glama

List my skills

list_my_skills
Read-onlyIdempotent

List Ready skills granted to this user, or select state=draft to list only this user's authored Drafts.

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

Input Schema

NameRequiredDescriptionDefault
limitNoPage size. Defaults to 20.
queryNoOptional search text.
stateNoReturn governed Ready skills by default, or only Drafts authored by this user.
cursorNoOpaque cursor returned by the previous page.

Output Schema

NameRequiredDescriptionDefault
dataYes
viewYes
workspaceNo
generated_atYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description usefully adds the visibility semantics of what records appear (granted vs authored) but says nothing about pagination behavior, page-size default, or ordering, despite a cursor/limit scheme in the schema. Valuable but only partial beyond the annotations.

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?

A single well-formed sentence with the default behavior front-loaded and the alternate mode immediately after. No filler, no restatement of the title.

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 a full output schema, rich annotations, and 100% parameter coverage, the description needs only to pin down which collection of skills is returned, which it does. The only shortfall is the absence of any steering toward sibling search/list tools for differing access patterns.

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%, so all four parameters, including the state enum and its two meanings, are already documented in structured data. The description reinforces state=draft but adds no syntax, default, or interaction detail beyond the schema. Baseline 3 applies.

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 a specific verb ('List') and resource ('Ready skills granted to this user'), and adds a second mode ('state=draft ... this user's authored Drafts'), so the agent knows exactly what set of records comes back. It does not differentiate against siblings such as search_skills or list_collections, which keeps it out of 5 territory.

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 clearly implies the condition that selects each mode — default lists granted Ready skills, state=draft lists authored Drafts — which is real usage guidance. However, it offers no guidance versus alternatives like search_skills (for text-based lookup) despite a 'query' parameter being present, so the agent must infer when to reach for those instead.

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