Skip to main content
Glama

emet_pages

Read-onlyIdempotent

List current area documents. For each area: line count, stale count, and the time of the newest source the page read. Read-only. Owner only. Computed on every call. The page body is not stored.

Instructions

List current area documents. For each area: line count, stale count, and the time of the newest source the page read. Read-only. Owner only. Computed on every call. The page body is not stored.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "emet_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the already-declared readOnly/idempotent/destructive hints, the description adds genuinely new behavior: owner-only access, recomputation on every call (no cache, so cost is non-trivial), and that the page body is not stored so only metrics come back. That last point alone prevents a wrong assumption about return content.

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?

Five short, front-loaded sentences that each carry distinct information (purpose, return fields, safety, auth, cost, caveat). Minor deduction for the telegraphic fragments and the unresolved pages/documents/areas wording, which costs a beat of clarity.

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?

With no input params and no output schema, the description correctly takes on the burden of describing what comes back and what does not (no body). It omits only the relationship to `emet_page`/`list_docs`, which is the one thing an agent still has to guess.

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

Parameters4/5

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

Zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The description does not waste words inventing parameter behavior that does not exist.

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 and resource ("List current area documents") and enumerates the returned metrics. It does not differentiate itself from the sibling `emet_page` (singular) or `list_docs`, and the terminology drifts between "pages", "area documents", and "areas", leaving mild ambiguity about what a unit is.

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?

"Owner only" gives a real access precondition, and "Read-only" frames it as a safe inspection call. But there is no explicit when-to-use versus the near-identical `emet_page` or `list_docs`; the agent must infer that this is the bulk/overview variant.

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