Skip to main content
Glama

ASO Studio Live Domain Audit & Self-Serve ASO Pack

Generate an edge router

generate_domain_aso_router
Read-onlyIdempotent

Generate a free starter router locally, targeting <15ms generation, for Cloudflare Worker, Next.js, FastAPI, Astro/Remix or Nginx. Returns code for four discovery routes; review before deployment. No network audit or deployment.

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": {
      "domain": "<domain>"
    },
    "name": "generate_domain_aso_router"
  }
}

Input Schema

NameRequiredDescriptionDefault
stackNoCloudflare Worker, Next.js/Vercel, FastAPI, Astro/Remix or Nginx.cloudflare
domainYesPublic domain, for example example.com; private hosts are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known; the description still adds real value by clarifying that generation happens locally, returns code rather than performing an audit or deploy, and should be reviewed before use. It leaves unclear whether generated files are persisted or only returned, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with the output artifact and target stacks front-loaded, followed by the review/deployment caveat. No filler; the latency target is the only borderline detail and it is at least a concrete expectation.

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 only two parameters, rich annotations, and no output schema, the definition covers what the tool produces ("code for four discovery routes"), what it does not do, and where it runs locally. The exact shape of the returned code is unspecified, but that is a minor gap for a starter generator.

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?

Schema coverage is 100%, so both `domain` and `stack` are already documented, including the enum values and the private-host rejection rule. The description only restates the stack list, adding no format or constraint detail beyond the schema, so the baseline 3 applies.

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?

The description names a specific verb and artifact ("Generate a free starter router locally") and immediately scopes it to five concrete target stacks plus "four discovery routes." An agent can tell this apart from the score/teardown/probe siblings without opening the schema, since none of them produce code.

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 clear usage context by stating the output is a starter requiring "review before deployment" and explicitly disclaims "No network audit or deployment," which prevents the agent from expecting a live audit. It does not name an explicit alternative tool or when-not-to-use condition, so it stops short of a 5.

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