server

Query the Waymark route map

waymark_query

Read-only

Before attempting a non-trivial task (API integration, vendor portal, checkout flow, multi-step web/tool procedure), query Waymark for routes other agents have documented and attested. Returns step sequences, known gotchas, and live success statistics. Use the returned route_id with waymark_attest after you finish.

Input Schema

TableJSON Schema

Name	Required	Description
`task`	Yes	Natural-language description of the task you are about to attempt
`limit`	No
`probe`	No	Set true only by Waymark's own smoke/eval/benchmark tooling so demand telemetry can separate internal probes from real agent queries
`domain`	No	Optional service/site hint, e.g. 'stripe.com'
`api_key`	No	Contributor API key (wmk_…) — only needed with verified_only. Get Pro at https://waymark.network/pricing
`verified_only`	No	Pro: return only individually fact-checked (verification:'verified') routes. Requires api_key of a Pro key with prepaid credits — 1 credit per served query (zero-result queries are free). Omit for normal free queries.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJul 10, 2026

addedInput schema / properties / api_key

Added value: +{
+  "description": "Contributor API key (wmk_…) — only needed with verified_only. Get Pro at https://waymark.network/pricing",
+  "maxLength": 200,
+  "type": "string"
+}

addedInput schema / properties / verified_only

Added value: +{
+  "description": "Pro: return only individually fact-checked (verification:'verified') routes. Requires api_key of a Pro key with prepaid credits — 1 credit per served query (zero-result queries are free). Omit for normal free queries.",
+  "type": "boolean"
+}

Changed1 schema field changedJul 9, 2026

addedInput schema / properties / probe

Added value: +{
+  "description": "Set true only by Waymark's own smoke/eval/benchmark tooling so demand telemetry can separate internal probes from real agent queries",
+  "type": "boolean"
+}

First observedJun 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Adds context beyond annotations: return contents (step sequences, gotchas, statistics), cost details for Pro queries, and that zero-result queries are free. No contradiction.

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 sentences, front-loaded with key information, no wasted words.

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?

Provides enough context for a read-only query tool with good annotations, though no output schema is present. Mentions what is returned but could detail output format more.

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 83%, and the description adds moderate context (e.g., api_key only needed with verified_only). Baseline 3 is appropriate.

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 clearly states the tool's purpose: querying Waymark for documented routes. It distinguishes from siblings by mentioning using the returned route_id with waymark_attest.

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 use before non-trivial tasks and to use waymark_attest after. Lacks explicit when-not-use guidance but is clear enough.

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

All server tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool serves a unique, well-defined purpose: querying routes, contributing procedures, attesting outcomes, and registering for API keys. No functional overlap exists.

Naming Consistency5/5

All tool names follow the consistent pattern 'waymark_<verb>', using snake_case and clear action verbs. The naming is uniform and predictable.

Tool Count5/5

Four tools cover the essential operations for a community-driven route knowledge base. The count is minimal yet complete, avoiding bloat.

Completeness5/5

The tool surface covers the full lifecycle: registration, querying existing routes, contributing new procedures, and attesting outcomes. No obvious gaps for the intended use case.

Resources

Need Help?