Skip to main content
Glama

Read page, JSON or KV value

get_page
Read-only

Read stored content: a page (rendered HTML, or its code or text), a JSON document or a KV value; long content is cut and continues by offset.

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": {
      "namespace": "<namespace>",
      "id": "<id>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
keyNoKV key
typeNoDefault html
offsetNoCharacter offset of the next part
passwordNo
namespaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / id / description
      Removed value: -"Page ID"
    • addedInput schema / properties / key
      Added value: +{
      +  "description": "KV key",
      +  "type": "string"
      +}
    • removedInput schema / properties / namespace / description
      Removed value: -"Page namespace"
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Character offset of the next part",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • removedInput schema / properties / password / description
      Removed value: -"Password if the page is protected"
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "Default html",
      +  "enum": [
      +    "html",
      +    "json",
      +    "kv"
      +  ],
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds genuinely non-redundant behavior — that long content is truncated and that `offset` is the continuation mechanism. That is more behavioral context than most read tools provide. It still omits what the `password` parameter gates and what happens when the page/key does not exist.

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?

One sentence, front-loaded with the verb and the three content kinds, then the truncation/continuation rule. No filler and no restatement of the title.

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 six-parameter read tool with no output schema and only half the parameters documented, the description leaves real holes: the meaning of required `namespace` and `id`, the `password` gate, and how one chooses between rendered HTML, code, and text for a page (no parameter appears to control that). The truncation rule is the main thing it does cover well.

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?

With 50% schema coverage the description does useful work: it clarifies `offset` as a continuation cursor and ties `type`/`key` to the content kinds returned. But the two most important unnamed parameters, required `namespace` and `id`, plus `password`, are left entirely to the schema, which itself carries no description for them.

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?

States a specific verb (read) and enumerates the resources it can return: a page (rendered HTML, code, or text), a JSON document, or a KV value. This maps cleanly onto the `type` enum, so an agent can tell what it will get. It does not, however, distinguish itself from the near-named sibling get_page_data, leaving the boundary implicit.

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 implied by content type (page vs JSON vs KV), which gives the agent a usable selection signal. There is no explicit when-to-use/when-not-to-use guidance and no named alternative such as get_page_data or get_guide, so the agent must infer the split from names alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.