Skip to main content
Glama

devtune_get_page_guard_rails

Read-onlyIdempotent

Get paginated page guard-rail classifications from the same bounded rollup used by DevTune. Pass url to read only the rows that apply to one page: the rows page protection checks before a change, matched on host without www., port, query or fragment, and on path with or without a trailing slash, under every tracked domain that covers it. Items then start with the most specific tracked domain, and target echoes the host and path the URL was read as. Any item with isUserLocked true means the page is locked. An empty list means DevTune holds no guard-rail row for that page, including pages outside the tracked domains; it does not show the page is unlocked or safe to change.

Input Schema

NameRequiredDescriptionDefault
urlNo
limitNoThe same setting as pageSize. Send either.
cursorNopagination.nextCursor from the previous page, unchanged. Keep the other arguments the same; omit it for the first page.
offsetNoDeprecated: pass cursor instead. Zero-based result offset.
pageSizeNoResults per page (1-100). Defaults to 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "pagination.nextCursor from the previous page, unchanged. Keep the other arguments the same; omit it for the first page.",
      +  "maxLength": 1024,
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "$ref": "#/properties/pageSize",
      +  "description": "The same setting as pageSize. Send either."
      +}
    • addedInput schema / properties / offset / description
      Added value: +"Deprecated: pass cursor instead. Zero-based result offset."
  2. Changed1 schema field changed
    • addedInput schema / properties / url
      Added value: +{
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds substantial extra context: URL normalization rules, domain-coverage behavior, item ordering (most specific domain first), target echo semantics, and the meaning of isUserLocked. The empty-list caveat ('does not show the page is unlocked') is a genuinely useful safety disclosure not derivable from structured fields.

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?

Front-loaded with the core purpose, then progressively details url matching, ordering, and empty-result semantics. A few clauses (e.g., 'under every tracked domain that covers it') are dense and could be tightened, but nothing is filler.

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?

No output schema exists, yet the description covers return shape (items begin with most specific domain, target echoes host/path, isUserLocked flag) and result interpretation. Combined with the pagination params in the schema, an agent has everything needed to invoke and read the result correctly.

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?

Schema coverage is 80% so limit/cursor/offset/pageSize are already documented. The description still adds real value for url by defining matching rules (host without www., no port/query/fragment, trailing-slash-insensitive path) and the target echo, which the schema does not express.

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?

States a specific verb and resource ('Get paginated page guard-rail classifications') and ties it to a defined source ('the same bounded rollup used by DevTune'), so an agent knows exactly what data this returns rather than just the tool name restated.

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

Usage Guidelines4/5

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

Explicitly says to pass url to narrow to a single page and defines the semantics of an empty result, which functions as a when-not signal. It does not name alternatives (e.g., page tracking / page metrics tools) for broader lookups, so it stops short of full routing guidance.

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.

Resources