Skip to main content
Glama

Edge Skills: star a skill

star_skill
Idempotent

Stars or unstars a skill or a collection for this user, so Edge remembers what worked: find_skill ranks a starred skill (and a starred collection's skills) first whenever it fits a task, and never shows it when it does not. Call it when the user asks ("star this", "save this one", "unstar it"), and also on your own when the user clearly liked a skill or collection or says they will reuse it (for example "perfect, I'll use this every week"); not just because a skill was used. Pass the Source and Skill that find_skill printed, or collection as the collection's name, id or getedge.cc/collections/ link; set starred to false to unstar. Reply with the returned line: it tells the user what was starred and how to undo it. Edge also stars a skill by itself when a rate_skill rating says it helped (and removes that star when a later rating says it did not); the rating's result says so. Unstarring removes such a star like any other, and EDGE_AUTO_STAR=off on the connector (or ?auto_star=off on the remote connector URL) stops automatic stars.

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

Input Schema

NameRequiredDescriptionDefault
skillNoThe Skill printed by find_skill. Required unless collection is given
sourceNoThe Source printed by find_skill, usually owner/repository. Leave it out only when the skill was in this session's last find_skill result
starredNotrue (the default) stars it; false unstars it
collectionNoTo star a collection instead of a skill: its name (creator/name), id or getedge.cc/collections/ link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / collection
      Added value: +{
      +  "description": "To star a collection instead of a skill: its name (creator/name), id or getedge.cc/collections/ link",
      +  "maxLength": 300,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / properties / skill / description
      Previous value: -"The Skill printed by find_skill"New value: +"The Skill printed by find_skill. Required unless collection is given"
    • changedInput schema / properties / starred / description
      Previous value: -"true (the default) stars the skill; false unstars it"New value: +"true (the default) stars it; false unstars it"
    • removedInput schema / required
      Removed value: -[
      -  "skill"
      -]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: the star changes find_skill ranking, unstarring reverses auto-stars granted via rate_skill, EDGE_AUTO_STAR=off / ?auto_star=off disables automation, and the returned line explains what was starred and how to undo it. It is slightly less clear on scope of the effect (per-user only) and on failure behavior, but the mutation semantics and reversibility are well covered despite destructiveHint=false being a near-miss for an unstar.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

All the content is relevant, but it is delivered as a single dense paragraph mixing trigger rules, parameter guidance, ranking effects, auto-star interplay, and an env-var escape hatch. Front-loading is good (what it does first), yet the auto-star/EDGE_AUTO_STAR tail could be tightened or split for scanability.

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 4-parameter toggle tool with no output schema, the definition covers when to call, how to call it, what changes downstream, and how to undo — including how to instruct the user via the returned line. Nothing an agent needs in order to invoke 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?

Schema coverage is already 100%, so the baseline is 3; the description nonetheless adds practical meaning by tying `skill`/`source` to values printed by find_skill and by spelling out the collection alternatives (name, id, or getedge.cc/collections/ link). It reinforces that starred=false unstars, but does not clarify the skill-vs-collection mutual exclusivity beyond what the schema field text already says.

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 pair ("Stars or unstars") plus the exact resource ("a skill or a collection for this user") and explains the effect on ranking. It is clearly separable from siblings like find_skill, rate_skill, and list_starred.

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 triggers ("Call it when the user asks ('star this', 'save this one', 'unstar it')"), proactive conditions (user clearly liked it or says they'll reuse it, with an example), and an explicit exclusion ("not just because a skill was used"). It also points to rate_skill as the separate auto-star path.

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