Skip to main content
Glama

read_favorites

Read-only

Retrieve the signed-in user's favorite LeafWiki pages so AI clients can reference saved pages in responses and workflows.

Instructions

The signed-in user's favorite pages.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuinely useful behavioral fact — the result is scoped to the signed-in user, so no user identifier is needed — but says nothing about ordering, result size, or what a favorite entry contains.

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?

One fragment with zero waste, but it is under-specified rather than tight: a verb like 'List' plus a note on what is returned would cost a few words and remove ambiguity. There is no structure to speak of beyond the single noun phrase.

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 no-parameter, read-only tool with annotations and no output schema, the description is close to sufficient, but it leaves open what a favorite page record looks like and whether results are ordered or truncated. Slightly more context would make the definition fully self-contained.

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 tool takes zero parameters, so there is no parameter semantics for the description to compensate for. The phrase 'signed-in user's' usefully clarifies that the subject is implicit in the session rather than supplied as input.

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 identifies the exact resource and its scope: favorite pages belonging to the signed-in user. It reads as a noun phrase without an explicit verb, but the read intent is unambiguous and clearly distinct from the write_favorite sibling.

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 guidance on when to call this versus alternatives such as read_page or write_favorite, and no prerequisites or exclusions are stated. The agent must infer that this is the retrieval path for favorites from the name alone.

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