Skip to main content
Glama

principia.priors.moderators

Read-only

One canonical prior's moderator groups (moderated_by[], levels in level order, marginal level named) plus the served-prior content ETag. Same ETag the REST route /api/v1/priors/// sends. Unmoderated priors return an empty list; nothing is invented.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "principia.priors.moderators"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
predicateNo
to_construct_idNo
from_construct_idNo

Output Schema

NameRequiredDescriptionDefault
etagYes
noteNo
foundYes
moderatedYes
moderated_byYes
canonical_prior_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / canonical_prior_id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / canonical_prior_id / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / etag / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / etag / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real value beyond that: the empty-list result for unmoderated priors, the guarantee that nothing is invented, and the ETag identity with the REST route, which lets an agent reason about caching and equivalence. It does not discuss failure modes for unknown priors, which keeps it short of a 5.

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?

Three compact sentences, front-loaded with the core resource and followed by the ETag and empty-case notes; no filler. The phrasing is dense and domain-specific ('levels in level order, marginal level named'), which is efficient for an informed agent but slightly opaque on first read.

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

Completeness3/5

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

An output schema exists, so the description is not obliged to enumerate return fields, yet it still usefully documents the moderator-group shape and the empty case. Annotations cover safety, so the main remaining gap is the unexplained parameter semantics for a four-parameter tool, which leaves the agent guessing how to construct a valid call.

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 description coverage is 0% across four parameters, so the description carries the full burden and largely does not meet it. The REST template `/api/v1/priors/<from>/<predicate>/<to>` indirectly maps from_construct_id, predicate, and to_construct_id, but the `id` parameter is never explained, and it is unclear whether `id` or the from/predicate/to triple is the intended selector given that zero parameters are required.

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 names a precise resource: the moderator groups of one canonical prior, including the level ordering convention and the served-prior ETag. It is clear what the tool fetches, but the verb is implicit (a noun phrase rather than an action), and it never contrasts itself with siblings like principia.canonical_priors.lookup, which also returns canonical prior data.

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

Usage Guidelines3/5

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

Usage is only implied by the resource description: fetch this when you need moderator groups for a prior. There is no explicit when-to-use, no when-not-to-use, and no named alternative for retrieving broader prior content. The note that unmoderated priors return an empty list is a helpful result-interpretation hint rather than routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources