Skip to main content
Glama

live_page

Fetches current values of blocks on a given page in read-only mode, with a configurable result limit to keep requests bounded.

Instructions

Current values of the blocks on a page (read only, limited number of requests).

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": {
      "page": "<page>"
    },
    "name": "live_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes
max_valuesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden and does contribute two useful facts: the operation is read only and it is rate limited. It omits what the response looks like, whether values are truncated, and what happens when the request budget is exhausted.

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?

A single short sentence with no filler, and the distinguishing scope is front-loaded. Its brevity comes at the cost of under-specification rather than efficient density.

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?

There is no output schema and no annotations, so the description should explain the return shape and parameter formats for a two-parameter read tool; it does neither. Only the rate-limit note fills a gap structured fields leave open.

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 coverage is 0%, so both parameters are undocumented structurally, and the description does not compensate: it never explains what form the page identifier takes or that max_values caps the returned values. The agent is left guessing at a required parameter's format.

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?

"Current values of the blocks on a page" names the resource (block values) and the scope (a single page), which distinguishes it from the historical sibling and from a single-block variant. It is a noun phrase rather than a verb+resource, but an agent can still tell what it returns.

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?

The parenthetical warns that this is read only and request-limited, but gives no when-to-use guidance, no prerequisites, and no explicit routing to alternatives. The agent must infer on its own when a live snapshot beats a historical query.

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