Skip to main content
Glama

read_find_title

Read-only

Finds pages by exact, case-insensitive title match and returns each page's path and ID for quick lookup.

Instructions

Pages whose title matches exactly (case-insensitive), with path and id.

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_find_title"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/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 does add real value beyond that by disclosing matching semantics (exact, case-insensitive) and the returned fields (path, id), but it is silent on duplicate-title behavior and on the empty-result case, which matter for an exact-match lookup.

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?

One compact sentence fragment with the matching rule front-loaded and no filler; every element (match rule, case sensitivity, returned fields) is load-bearing. It is terse to the point of reading like a fragment, but nothing is wasted.

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?

For a one-parameter read tool with no output schema, the description covers the match rule and the returned fields, which is close to sufficient. The remaining gap is edge-case behavior on missing or duplicate titles, which is minor at this complexity.

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 description coverage is 0%, so the single 'title' parameter relies entirely on prose, and the description does explain that matching is exact and case-insensitive. It does not clarify whitespace/trimming behavior or whether the empty string is rejected, though minLength:1 in the schema partially covers the latter.

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 the resource (pages) and the exact retrieval criterion (title matches exactly, case-insensitive) plus what comes back (path and id), so an agent can tell this is a title lookup rather than a full page fetch. It stops short of naming the sibling to use for partial/fuzzy matches (e.g. read_search) or path-based lookup, so differentiation is implied by the word 'exactly' rather than stated.

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?

Usage is only implied: 'matches exactly' signals this is the tool for precise title lookups and implicitly not for substring or ranked search, but no alternative tool or when-not condition is spelled out. There is no mention of prerequisites, ambiguity handling, or what to do when no page matches.

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