Skip to main content
Glama

excalibur-mcp

by io.github.lonniev

excalibur_scheduler_status

The scheduler's configuration and current status (free; any proven patron).

Relays the cron Worker's public /status — cadence, version, renewal window, and current authorization phase (pending / active / idle, no challenge phrase) — and adds the operator npub it acts for. No secrets: the pending phrase (operator-only) is scheduler_pending; the per-tick traffic log is get_scheduler_log. Returns the merged config, or {worker: "unavailable"} merged in if the Worker can't be reached.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
npubNoYour npub (npub1...).
dpop_tokenNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: returns cadence, version, renewal window, authorization phase, operator npub, and handles worker unavailability with an error object. It also explicitly states what is not returned (pending phrase, traffic log).

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?

The description is a single dense paragraph that packs a lot of information without excess, but could benefit from clearer separation of sections.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema and the detailed description covering return values, error handling, and related tools, the description is complete and sufficient for agent understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% (npub described, dpop_token not), and the description adds no parameter details. It does not compensate for the missing dpop_token description or clarify usage of the two parameters.

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 it retrieves the scheduler's configuration and current status, using the verb 'relays' and specifying the resource (cron Worker's /status). It distinguishes from sibling tools by directing the pending phrase to scheduler_pending and traffic log to get_scheduler_log.

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?

The description implicitly suggests when to use this tool (to get status) and mentions alternatives (scheduler_pending, get_scheduler_log) for specific data, but does not explicitly state when not to use it or prerequisites.

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

All excalibur-mcp 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

A3.6/5.0
Disambiguation5/5

Each tool targets a distinct operation and domain (account, posts, coupons, credentials, scheduling, oracle, etc.), with clear differentiation even for similar-sounding tools like check_balance vs check_authority_balance or list_coupons vs list_my_coupons. There is no ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern (e.g., create_post, delete_coupon, list_posts), with no mixing of styles. The excalibur_ prefix is uniform.

Tool Count1/5

With 72 tools, the server far exceeds the typical well-scoped range (3–15). While the functionality is broad, the sheer number feels excessive for a single MCP server, leading to an extreme mismatch.

Completeness5/5

The tool surface covers the full lifecycle for core domains: CRUD for posts, snippets, coupons, credentials; complete flows for OAuth, npub proof, scheduling, notarization, and payments. No obvious gaps are present.

Resources