Skip to main content
Glama

quartermaster

by app.surewhynot.quartermaster

x402_router

START HERE. One tool for anything x402, Base chain, or web/AI: describe your goal in plain English (q) and Quartermaster picks and runs the right underlying tool, returning the answer plus which tool it used. Examples: 'audit https://api.example.com/paid', 'price of eth', 'is 0x… a contract', 'verify settlement 0x…', 'search the bazaar for weather'. Use this when you don't want to choose among the individual tools below. Costs $0.03 (USDC via x402).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesYour goal in plain English

TDQS

A4.3/5.0
Behavior3/5

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

No annotations exist, so description carries burden. It discloses cost ($0.03 USDC), that it selects a tool and returns the answer plus tool name. However, it does not mention potential side effects, failure modes, or that it may call external APIs.

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?

Description is relatively concise, providing key information in a few sentences with examples. Could be slightly more structured but overall effective.

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?

Given the complexity of being a router over many sibling tools, the description covers purpose, usage, cost, and return format. It lacks details on error handling or rate limits but is sufficient for an agent to use correctly.

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 already covers the parameter q with 'Your goal in plain English' (100% coverage). Description adds semantic value by explaining that q is interpreted to route to an appropriate tool, going beyond the schema's basic description.

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 that the tool is a router for 'anything x402, Base chain, or web/AI', picking and running the correct underlying tool. This distinguishes it from sibling tools that are specific utilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use ('Use this when you don't want to choose among the individual tools below') and positions it as 'START HERE'. Examples further clarify typical queries.

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

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

B3.1/5.0
Disambiguation3/5

Several tools have overlapping purposes, such as multiple x402 transaction verification tools (payment_proof, settlement_assurance, tx_status) and multiple summarization tools (summarize_url, tldr_text). However, descriptions provide enough detail to differentiate them, though an agent could still be confused.

Naming Consistency2/5

Tool names are inconsistent, mixing verb_noun patterns (e.g., summarize_url, generate_uuid) with noun phrases (e.g., base64, dns_lookup) and inconsistent prefixes (e.g., base_token_info vs base_allowance vs base64). The x402_* group is consistent, but overall naming lacks a unified pattern.

Tool Count2/5

With 49 tools, the server is very heavy. While it aims to be a broad utility server, this number exceeds typical well-scoped servers (3-15 tools) and risks being overwhelming for agents, especially given the mix of unrelated domains.

Completeness3/5

The server covers a wide range of utilities (crypto, AI, web, dev, x402 payments) but lacks depth in any single area. For instance, there are many read-only tools but few state-changing operations beyond x402. Gaps like file handling or database access are expected given its scope.

Resources