DevTune MCP

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.

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": "devtune_get_page_guard_rails"
  }
}

Input Schema

Name	Required	Description
`url`	No
`limit`	No	The same setting as pageSize. Send either.
`cursor`	No	pagination.nextCursor from the previous page, unchanged. Keep the other arguments the same; omit it for the first page.
`offset`	No	Deprecated: pass cursor instead. Zero-based result offset.
`pageSize`	No	Results per page (1-100). Defaults to 25.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 10, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / limit / $ref
```
Removed value: -"#/properties/pageSize"
```
- addedInput schema / properties / limit / maximum
```
Added value: +100
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- addedInput schema / properties / limit / type
```
Added value: +"integer"
```
- addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```

Changed3 schema fields changedOct 25, 2026

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."

Changed1 schema field changedOct 23, 2026
- addedInput schema / properties / url
```
Added value: +{
+  "type": "string"
+}
```
First observedSep 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuinely non-obvious behavior: ordering by most-specific tracked domain, the meaning of isUserLocked, and the critical warning that an empty list does not mean the page is unlocked or safe. It omits rate limits or payload size expectations.

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 packed with useful scoping detail; almost no filler. The downside is that it is one dense block with no sentence breaks or bullets, making the matching rules and the empty-list caveat harder to scan than necessary.

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?

No output schema exists, so the description carries the return-shape burden, and it does describe items, ordering, the target echo field, and isUserLocked. A mutation-free read tool with a fully described url filter is adequately covered, though it never enumerates the classification fields an item contains.

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%, and the one undocumented parameter, url, gets a thorough explanation of matching semantics: host normalized without www./port/query/fragment, path with or without trailing slash, matched across every covering tracked domain. That is meaning well beyond the bare "type: string" in the schema. The offset/limit/pageSize aliasing is left to the schema, which handles it.

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: "Get paginated page guard-rail classifications," and grounds it in "the same bounded rollup used by DevTune," which tells the agent the data source. It does not name a sibling to contrast with, so differentiation from tools like devtune_get_page_tracking is left 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?

Explains how to use the tool ("Pass url to read only the rows that apply to one page") and how to interpret an empty result, which is real usage guidance. It never says when to choose this over an alternative guard-rail or page tool, nor lists exclusions, so the agent must infer routing.

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

All DevTune MCP 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.

Resources

Need Help?