Skip to main content
Glama

Seneschal Data

by io.github.Rotwang9000

Agent directory (Gopher-over-HTTPS)

seneschal_agent_directory

Terse, drill-down discovery index of this ecosystem (Seneschal, FlashBank, winbit32, secresea, ZecBus, Zecmon, Ziving, Bit ID, McPai) plus a LIVE mirror of the official MCP registry (registry.modelcontextprotocol.io) — the same directory served over HTTPS at https://seneschal.space/.well-known/agent.gopher, callable here so you never leave the MCP session. Start with section="root" to see the top-level menu, then call again with section="seneschal"/"flashbank"/"winbit32"/"secresea"/"zecbus"/"zecmon"/"ziving"/"bitid"/"mcpai" to drill into a project. Each project exposes About / Agents / Actions — drill them with section="/about", "/agents" or "/actions" (e.g. "winbit32/actions"). Seneschal additionally drills into its own services with section="seneschal/" where is one of private-watch, checkout, oracle, shovels, builder, data, paymaster, board, ironwood, mcp — every website + MCP capability, grouped and priced. section="registry" browses connectable third-party MCP servers (use cursor to page); section="about"/"agents" is the directory’s own prose. format="gopher" (default) is the compact RFC-1436 menu; format="json" returns a structured {title, items[]}. A discovery layer, not a replacement for MCP — use it to FIND tools, then connect. Free, no payment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPagination cursor for the "registry" section, taken from a previous "More servers" entry.
formatNo"gopher" (default) = compact menu text; "json" = structured {title, items[]}.
sectionNoWhich directory node to fetch. Default "root". Top level: root, seneschal, flashbank, winbit32, secresea, zecbus, zecmon, ziving, bitid, mcpai, registry, about, agents. Drill a project with "<site>/about", "<site>/agents" or "<site>/actions" (e.g. "winbit32/actions"). Seneschal also exposes per-service sections: "seneschal/private-watch", "seneschal/checkout", "seneschal/oracle", "seneschal/shovels", "seneschal/builder", "seneschal/data", "seneschal/paymaster", "seneschal/board", "seneschal/ironwood", "seneschal/mcp".

Schema Changelog

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

  1. Changed1 schema field changed
    • changedInput schema / properties / section / description
      Previous value: -"Which directory node to fetch. Default \"root\". Top level: root, seneschal, flashbank, winbit32, secresea, zecbus, registry, about, agents. Drill a project with \"<site>/about\", \"<site>/agents\" or \"<site>/actions\" (e.g. \"winbit32/actions\"). Seneschal also exposes per-service sections: \"seneschal/private-watch\", \"seneschal/checkout\", \"seneschal/oracle\", \"seneschal/shovels\", \"seneschal/builder\", \"seneschal/data\", \"seneschal/paymaster\", \"seneschal/board\", \"seneschal/ironwood\", \"seneschal/mcp\"."New value: +"Which directory node to fetch. Default \"root\". Top level: root, seneschal, flashbank, winbit32, secresea, zecbus, zecmon, ziving, bitid, mcpai, registry, about, agents. Drill a project with \"<site>/about\", \"<site>/agents\" or \"<site>/actions\" (e.g. \"winbit32/actions\"). Seneschal also exposes per-service sections: \"seneschal/private-watch\", \"seneschal/checkout\", \"seneschal/oracle\", \"seneschal/shovels\", \"seneschal/builder\", \"seneschal/data\", \"seneschal/paymaster\", \"seneschal/board\", \"seneschal/ironwood\", \"seneschal/mcp\"."
  2. Changed1 schema field changed
    • changedInput schema / properties / section / description
      Previous value: -"Which directory node to fetch. Default \"root\". Top level: root, seneschal, flashbank, winbit32, secresea, zecbus, registry, about, agents. Drill a project with \"<site>/about\", \"<site>/agents\" or \"<site>/actions\" (e.g. \"winbit32/actions\"). Seneschal also exposes per-service sections: \"seneschal/private-watch\", \"seneschal/oracle\", \"seneschal/shovels\", \"seneschal/builder\", \"seneschal/data\", \"seneschal/paymaster\", \"seneschal/board\", \"seneschal/mcp\"."New value: +"Which directory node to fetch. Default \"root\". Top level: root, seneschal, flashbank, winbit32, secresea, zecbus, registry, about, agents. Drill a project with \"<site>/about\", \"<site>/agents\" or \"<site>/actions\" (e.g. \"winbit32/actions\"). Seneschal also exposes per-service sections: \"seneschal/private-watch\", \"seneschal/checkout\", \"seneschal/oracle\", \"seneschal/shovels\", \"seneschal/builder\", \"seneschal/data\", \"seneschal/paymaster\", \"seneschal/board\", \"seneschal/ironwood\", \"seneschal/mcp\"."
  3. Changed1 schema field changed
    • changedInput schema / properties / section / description
      Previous value: -"Which directory node to fetch. Default \"root\". Top level: root, seneschal, flashbank, winbit32, secresea, zecbus, registry, about, agents. Drill a project with \"<site>/about\", \"<site>/agents\" or \"<site>/actions\" (e.g. \"winbit32/actions\")."New value: +"Which directory node to fetch. Default \"root\". Top level: root, seneschal, flashbank, winbit32, secresea, zecbus, registry, about, agents. Drill a project with \"<site>/about\", \"<site>/agents\" or \"<site>/actions\" (e.g. \"winbit32/actions\"). Seneschal also exposes per-service sections: \"seneschal/private-watch\", \"seneschal/oracle\", \"seneschal/shovels\", \"seneschal/builder\", \"seneschal/data\", \"seneschal/paymaster\", \"seneschal/board\", \"seneschal/mcp\"."
  4. Changed2 schema fields changed
    • changedInput schema / properties / section / description
      Previous value: -"Which directory node to fetch. Default \"root\"."New value: +"Which directory node to fetch. Default \"root\". Top level: root, seneschal, flashbank, winbit32, secresea, zecbus, registry, about, agents. Drill a project with \"<site>/about\", \"<site>/agents\" or \"<site>/actions\" (e.g. \"winbit32/actions\")."
    • removedInput schema / properties / section / enum
      Removed value: -[
-  "root",
-  "seneschal",
-  "flashbank",
-  "winbit32",
-  "secresea",
-  "registry",
-  "about",
-  "agents"
-]
  5. Added

TDQS

A4.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses the read-only discovery nature, format behavior (gopher vs json), pagination via cursor, and the live mirror aspect. It does not explicitly state 'no side effects', but the tool's purpose as a directory makes this clear. Adding an explicit read-only note would improve transparency.

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 long but front-loaded with the core purpose and structured with lists and code-like examples. Some redundancy exists (e.g., section values repeated in schema), but the breadth of the tool justifies the length. Every sentence earns its place, though it could be trimmed slightly.

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?

For a three-parameter tool with 100% schema coverage and no output schema, the description is exhaustive: all section options, formatting options, pagination semantics, and explicit examples. It even covers the JSON return shape. No gaps remain.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds substantial value beyond it. It provides concrete example sections ('winbit32/actions'), lists all available section values, explains cursor usage for registry pagination, and clarifies the difference between gopher and json outputs. This far exceeds the schema's parameter descriptions.

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 explicitly identifies the tool as a 'discovery index' and 'LIVE mirror of the official MCP registry', with a clear verb ('browse', 'drill-down') and resource. It distinguishes itself from sibling tools (board, checkout, etc.) by positioning itself as a directory to find tools rather than a transactional service.

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?

It provides explicit usage instructions: 'Start with section="root"', then drill down with specific section patterns, and warns 'not a replacement for MCP — use it to FIND tools, then connect.' This gives clear when-to-use and an exclusion, differentiating it from direct tool invocations.

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

All Seneschal Data 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.9/5.0
Disambiguation4/5

Tools are grouped by domain (board, private_watch, zecmon) with clear lifecycle separation, but seneschal_list_at_risk_borrowers and seneschal_list_borrowers overlap heavily, and the USDC vs crypto variants of private_watch_create/topup could be confused without careful reading.

Naming Consistency4/5

Most tools follow a seneschal_<domain>_<action> pattern, but verb/noun order varies (get_borrower vs list_borrowers vs board_list) and outliers like seneschal_health and seneschal_q break the pattern.

Tool Count3/5

At 35 tools, the server is definitely heavy, but it covers multiple distinct domains (DeFi data, privacy-chain monitoring, notice boards, payments), so the count is at the high end of reasonable rather than absurdly bloated.

Completeness4/5

Core workflows are well covered: borrower discovery/analysis, liquidations, private watch lifecycle, Zcash scanning lifecycle, board operations, and checkout invoices. Minor gaps like board deletion or watch cancellation exist but are workaround-able.

Resources