Skip to main content
Glama

Star take

star_take

Mark a take as the item's chosen one (the item's starred_take_id). item is its id, slug or @slug; take_id comes from list_takes. Returns the take.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>",
      "item": "<item>",
      "take_id": "<take_id>"
    },
    "name": "star_take"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
projectYes
take_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description adds real value by disclosing the exact field mutated (`starred_take_id`), implying a single-star model where a prior star is superseded, and stating the return ('Returns the take'). It does not disclose failure behavior (e.g. take not in item) or whether the prior star is cleared, which keeps it below a 5.

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?

Two compact sentences with the state change front-loaded, followed by parameter sourcing and return value. Nothing is redundant and no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the return value needn't be spelled out, and the mutation's safety profile is covered by annotations. Still, for a 3-required-parameter mutation the description leaves `project` undocumented and omits what an agent needs to know about overwriting an existing starred take.

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?

With 0% schema description coverage, the description carries the parameter burden: it explains `item` accepts an id, slug, or `@slug`, and that `take_id` comes from list_takes. The third required parameter, `project`, is never described at all, so compensation is only partial.

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 definition names a specific verb and resource ('Mark a take as the item's chosen one') and even identifies the field it writes (`starred_take_id`), which is unambiguous. It stops short of a 5 because it doesn't position itself against any sibling (e.g. no mention of whether an unstar operation exists elsewhere).

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 provides one useful routing hint — `take_id` comes from list_takes — which tells the agent the precursor call needed. However, it gives no guidance on what happens when the item already has a starred take (replacement vs. error), nor any precondition about ownership or project access.

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