remnus

get_pages

Read-only

Read several pages/rows by id in one call, for a known, possibly mixed id list. A bad id fails only its own entry — check each "ok". For rows of one database use query_database with filters/fields instead: one query, not N lookups.

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": {
      "pageIds": "<pageIds>"
    },
    "name": "get_pages"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	As in get_page	full
`pageIds`	Yes

Output Schema

Name	Required	Description	Default
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 24, 2026

changedInput schema / properties / mode / description

Previous value: -"Same as get_page — \"outline\" collapses each body to headings + first line per section"New value: +"As in get_page"

removedInput schema / properties / pageIds / description
```
Removed value: -"Page/row IDs to fetch (max 50)"
```

AddedSep 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description doesn't need to repeat that. It adds valuable behavioral detail: 'A bad id fails only its own entry — check each "ok"', which discloses partial failure semantics not present in annotations. No contradiction.

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?

Two sentences with no waste. The core purpose is front-loaded, followed by the alternative and a failure-behavior note. Every clause earns its place.

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

Completeness5/5

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

Given the tool's complexity (batch read, partial failure) and the presence of an output schema, the description covers the essential points: what it does, when to use an alternative, and failure handling. The 50-item limit is in the schema, so no need to repeat. Nothing critical is missing.

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 50% (mode has a description, pageIds does not). The description clarifies that pageIds are ids and can be mixed, adding context beyond the schema. However, it does not elaborate on the mode parameter or its effect, leaving some semantics to the schema reference ('As in get_page').

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

Purpose5/5

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

The description states a specific action ('Read several pages/rows by id in one call') with a clear resource and scope. It distinguishes itself from get_page (single) and query_database (filtered) by emphasizing batch retrieval for a known, mixed id list.

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

Usage Guidelines5/5

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

Explicitly names the alternative (query_database) and gives the condition for when to use it instead ('For rows of one database use query_database with filters/fields instead: one query, not N lookups'). This provides clear when-to-use and when-not-to-use guidance.

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

All remnus tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.