Skip to main content
Glama
arctop

Seamless

by arctop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

favorite_set

Idempotent

Star or unstar items to sort favorites first, pin them in session briefings, and boost recall rank without changing update time.

Instructions

Star or unstar an item. Favorites sort first in the console, are pinned into session briefings (memories), and get a mild recall rank boost. For memories and notes the flag is stored in the file's frontmatter; starring never bumps an item's updated time.

Input Schema

NameRequiredDescriptionDefault
idYesthe item's identifier: memory name, note id (or slug), project slug, plan slug, task id, session id (or name), trial id
kindYeswhat kind of item to star
projectNoproject scope for memory-name/note-slug resolution; defaults to the bound session's project
sessionNothe session to act as: the name session_start returned, the cc/<id> or cx/<id> on your briefing's 'Seam session' line, or a session ULID. It scopes and credits this call. Defaults to this connection's session; pass it on every call when session_start reports the connection as stateless
favoriteYestrue to star, false to unstar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.4
    • addedInput schema / properties / session
      Added value: +{
+  "description": "the session to act as: the name session_start returned, the cc/<id> or cx/<id> on your briefing's 'Seam session' line, or a session ULID. It scopes and credits this call. Defaults to this connection's session; pass it on every call when session_start reports the connection as stateless",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare mutation (readOnlyHint=false), idempotency, and non-destructiveness. The description adds real context beyond that: the flag lives in frontmatter for memories/notes, and starring never bumps the item's updated time — a side-effect disclosure that matters for an idempotent mutation. It does not cover permissions or how non-file kinds (project, plan, task, session, trial) persist the flag.

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?

Three sentences, action front-loaded, each carrying distinct information (what it does, why it matters, how it is stored). No filler or restatement of the name.

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 a mutating tool, the description adequately covers effect, storage mechanism, and a key side effect (updated time unchanged). It leaves open where the flag is stored for non-file kinds and whether any permission or scope rules apply, which is a minor but real gap.

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 coverage is 100%, so every parameter including the enum and the session/project scoping rules is already documented in the schema. The description only touches parameter semantics indirectly by explaining frontmatter storage for the memory and note kinds; 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?

States a specific verb pair (star/unstar) and resource (item), and enumerates the effects. No sibling tool performs favoriting, so it is unambiguously distinct from memory_write, notes_update, tasks_update, and the rest of the list.

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?

The description explains what favoriting achieves (console sort order, session-briefing pinning, recall rank boost), which implies when an agent would want it, but it never states when to use this versus leaving an item unfavorited or naming any alternative approach. Usage is inferred rather than directed.

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

Deploy Server

Other Tools