Skip to main content
Glama

NS Pros MCP Gateway

cloudflare-docs__migrate_pages_to_workers_guide

ALWAYS read this guide before migrating Pages projects to Workers.

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": "cloudflare-docs__migrate_pages_to_workers_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It discloses that this is a read-only guide to consult first, but says nothing about return format, length, or whether it merely links versus fully explains migration steps. For a zero-parameter fetch the risk is low, but the behavior is only partly described.

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?

A single imperative sentence, front-loaded with the key directive, with no filler. The all-caps 'ALWAYS' is slightly shouty but does convey the prerequisite ordering.

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 zero-param guide tool with no output schema and no annotations, the description tells the agent when to invoke it but not what it returns or how large the output is. Enough to decide to call it, but thin on expectations for the response.

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?

The tool takes no parameters, so there is nothing for the description to clarify; the baseline is 3-4. It correctly implies no inputs are needed, but adds no constraint language such as whether an argument could target a specific section.

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?

The description names a specific resource (a migration guide) and its subject (moving Pages projects to Workers), so an agent can tell what it will get. It does not explicitly say it returns documentation content, which leaves the verb slightly implicit.

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?

It gives a clear trigger: read before migrating Pages projects to Workers, with the emphatic 'ALWAYS' marking it as a prerequisite. It stops short of naming an alternative for documentation lookup (e.g. a search tool) or stating when the guide is unnecessary.

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.