Skip to main content
Glama

read_slug

Read-only

Generates the unique LeafWiki slug for a title under an optional parent, letting editors preview the page path before creating or linking a page.

Instructions

The slug LeafWiki would give a title, unique under its parent (editors only).

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": {
      "title": "<title>"
    },
    "name": "read_slug"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
parentNoParent id or path; omit for the top level

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/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 safe, local-computation profile is established. The description adds useful context beyond that by flagging the '(editors only)' permission requirement, but does not say whether this is a pure calculation or a lookup, nor what happens if the title is already taken.

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

Conciseness4/5

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

A single compact sentence with no wasted wording, and the key qualifier ('unique under its parent') is placed early. The terseness borders on cryptic, but nothing is padded.

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 no output schema, the description should state that a slug string is returned and roughly how normalization works, since no structured field covers return values. It covers inputs and permissions but leaves the output ambiguous.

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% and the 'title' parameter has no schema description, but the phrase 'unique under its parent' adds real semantics: it explains why parent scoping affects the generated slug, partially compensating. The schema already documents 'parent' as 'Parent id or path; omit for the top level', so the description's remaining contribution is modest.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (the slug LeafWiki assigns to a title, scoped to a parent) but is phrased as a noun fragment with no verb, so it never explicitly says the tool 'returns' or 'computes' a slug. An agent can infer the intent, but it doesn't cleanly separate this from the sibling read_find_title.

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?

Only the parenthetical '(editors only)' gives any situational cue, and that is a permission note rather than when-to-use guidance. There is no mention of when to prefer this over read_find_title or read_lookup_path, nor any exclusions.

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