Skip to main content
Glama
Sign In

mowteng

by app.mowteng
OverviewDiscussionsAdmin

Set up IndexNow for a site

indexnow_setup
Read-only

Everything a site needs for indexnow_submit: its IndexNow key from mowteng (the same on every call, nothing stored), the file to upload with a download link, where it goes, and whether it is live on the site yet. Once it is live, indexnow_submit needs no key for this site. Run it again after uploading to check.

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": {
      "site": "<site>"
    },
    "name": "indexnow_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site: a URL on it such as "https://www.example.com/", or a Search Console property such as "sc-domain:example.com"

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, it discloses that the key is identical on every call and nothing is stored server-side, and it describes the returned verification state. That is genuine behavioral context an agent could not infer from readOnlyHint/openWorldHint alone. It does not describe what the download link looks like or how long it stays valid.

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?

Two sentences, front-loaded with what the tool yields, followed by the follow-up workflow. The parenthetical '(the same on every call, nothing stored)' is slightly awkward but earns its place by answering the natural question of key stability. No filler.

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?

There is no output schema, so the description carries the return-value burden, and it does enumerate the four things returned (key, file, location, live status). Combined with one fully documented parameter and the sibling reference, an agent has enough to call it correctly; only link lifetime and error cases are unaddressed.

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% for the single 'site' parameter, including both URL and Search Console property forms, so the schema already carries the semantics. The description adds no further detail about site formats and merely references the site implicitly. Baseline 3 applies.

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 states concretely what the tool returns: the IndexNow key, the verification file to upload with a download link, its destination, and whether it is live. That resolves the ambiguity in the title 'Set up', which could otherwise be read as an action verb, and it distinguishes the tool from indexnow_submit by framing it as the prerequisite. The odd reference to 'mowteng' as the key source is unexplained, adding a small amount of noise.

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 workflow condition: call this before indexnow_submit, and once the file is live, indexnow_submit needs no key for that site. It also says to re-run after uploading to check status. It does not state a when-not-to-use case (e.g. for sites already verified), but the sequencing guidance is explicit and actionable.

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

All mowteng toolsInspect
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