Skip to main content
Glama

read_pages_by_property

Read-only

Retrieve LeafWiki pages that define a specific property, optionally filtered to one value, to locate pages sharing metadata.

Instructions

Pages that set a property, optionally to one value.

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": {
      "key": "<key>"
    },
    "name": "read_pages_by_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
valueNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.4/5.0
Behavior2/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. Beyond that the description adds nothing behavioral: no ordering, result limits, pagination, or handling of pages whose property is unset. The one useful nuance it could have stated, exact-match versus presence-only filtering, is left ambiguous.

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?

It is very short and front-loads the subject, so nothing is padded. However, it is a sentence fragment that trades clarity for brevity, and the trailing "optionally to one value" is awkward enough to require re-reading.

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

Completeness2/5

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

The tool is low complexity (two params, no output schema, no nesting), so the description does not need to be long, but it should at least name the required key and confirm the return is a page collection. As written an agent must guess both the filter semantics and the output shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter burden and it largely does not. It hints that the value parameter narrows to a single value, but never explains that "key" is the property name that is required, nor whether matching is exact, case-sensitive, or type-aware.

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 fragment "Pages that set a property, optionally to one value" conveys a filter concept and implies a list of pages, but supplies no explicit verb (list/read/query) and never states what is returned. An agent can infer the shape because of the tool name, not because the description clarifies it.

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 guidance, no when-not-to-use, and no mention of the adjacent retrieval tools such as read_pages_by_tags or read_properties that an agent would have to choose between. The only hint is the word "optionally," which is about parameters, not tool selection.

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