Skip to main content
Glama

Edge Skills: list my starred skills

list_starred
Read-onlyIdempotent

Only when the user asks to see their starred, favourite or saved skills or collections (for example "show my starred skills"): lists them with source, a one-line description and the skill's getedge.cc page when it has one, including skills Edge starred because they helped. Never call it on your own initiative.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent and non-destructive, so the safety profile is settled. The description adds value beyond that by disclosing the shape of the response and the non-obvious inclusion of skills 'Edge starred because they helped'. It does not mention pagination or result-size limits, which is the only notable gap.

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?

The gating condition is correctly front-loaded before the description of the output, and the closing prohibition is short and imperative. The middle clause is dense, stacking output fields and the 'starred because they helped' nuance into one long sentence, but every element carries information.

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?

With no parameters, no output schema and no nested objects, the description carries the full burden and does so: it names the trigger, the population of results, and the per-entry fields. Nothing an agent needs in order to call it correctly is missing.

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 input schema has zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description sensibly spends its words on scope and output instead of parameters.

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 them') scoped to the user's starred/favourite/saved skills and collections, and spells out what each entry contains (source, one-line description, getedge.cc page). This clearly separates it from the sibling mutation star_skill and from the search-oriented find_skill.

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 an explicit trigger condition with a concrete user utterance example, and an explicit exclusion ('Never call it on your own initiative'). An agent knows both when to call it and when to leave it alone without consulting anything else.

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