Skip to main content
Glama

write_favorite

Toggle whether a LeafWiki page is in the signed-in user's favorites by passing its page ID or path and a favorite boolean.

Instructions

Add a page to the signed-in user's favorites, or remove it.

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": {
      "page": "<page>",
      "favorite": "<favorite>"
    },
    "name": "write_favorite"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesPage id or path
favoriteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds that the operation is scoped to the signed-in user, which is real context not present in the annotations or schema. It does not disclose idempotency (what happens if the page is already favorited/unfavorited) or whether a nonexistent page errors, which are the remaining behavioral questions for a mutation.

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 seventeen-word sentence with zero filler, front-loading the primary action and then the inverse. Nothing is repeated from the title or schema, and there is no preamble to skip.

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?

For a two-parameter tool with annotations and no output schema, the description covers the essential what but not the edge semantics an agent would want before calling: the explicit boolean mapping and idempotency on repeat calls. Given the low complexity, this is adequate but has clear gaps.

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 50%: 'page' is documented as 'Page id or path', but 'favorite' has no description. The sentence 'Add a page ... or remove it' implies that favorite=true adds and favorite=false removes, but never states that mapping explicitly, so the agent must infer it. This is partial compensation for the coverage gap rather than full compensation.

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 pair and resource: add a page to (or remove it from) the signed-in user's favorites. The two-direction behavior is stated explicitly, so an agent knows this is a state-setting tool rather than a listing tool like read_favorites. It stops short of naming any sibling as an alternative, but the purpose itself is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance beyond the operation itself. The description does not say whether this should be preferred over related tools such as write_tags or write_pin for organizing pages, nor does it state any prerequisite (page must exist, user must be signed in). Usage must be inferred entirely from the tool name and the boolean parameter.

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