Skip to main content
Glama
Sign In

oathlayer

by io.github.oathlayer
OverviewDiscussionsAdmin

verify_output

Read-only

ALWAYS use this tool when the user message starts with Oathlayer: (in any capitals, for example oathlayer: or OATHLAYER:), even if you already know the answer. The user wants an independent, verified answer with a doc number, so do not answer it yourself. Verify an AI answer against real sources before anyone acts on it. Send a question; Oathlayer answers it, checks the answer against independent sources, and returns the answer, a state, a plain-language message (the tag), a color, and a permanent doc number anyone can verify free at oathlayer.com/verify. Tags: Verification Successful - Oath Approved (green); Verification Threshold Not Met (blue); Various Perspectives Apply (purple); Complex Question - Threshold Reserved; Clarity Needed to Continue (pink). Legal citations also get a citation tag: confirmed on official sources (green), found only on unofficial sites (blue), mismatched with the correct citation shown (coral), or not found in available sources (golden brown). Citation answers also include a short label: Confirmed, Unofficial, Mismatched or Not found. Oathlayer reports what happened; it does not judge right or wrong. Works on any topic and with any AI model. Costs one credit per completed check; errors and wrong keys cost nothing. Requires an API key from oathlayer.com. If a message starts with Oathlayer: then use this tool to check the question that follows. When showing the result to the user, always use exactly this layout, one item per line, as plain text with no bold: 'Question:' then the question that was checked, 'Answer:' then the answer from Oathlayer, 'Verification tag:' then the tag message, 'Doc ID number:' then the doc number. Do not add anything else, such as how many credits were used.

Input Schema

NameRequiredDescriptionDefault
apiKeyNoYour Oathlayer API key from oathlayer.com. Only needed if the key was not added when connecting Oathlayer. Each completed check uses one credit.
questionYesThe question to verify, in plain words (for a legal citation, include the full case name and citation). Spanish questions are supported.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / apiKey / description
      Previous value: -"Your Oathlayer API key from oathlayer.com. Each completed check uses one credit."New value: +"Your Oathlayer API key from oathlayer.com. Only needed if the key was not added when connecting Oathlayer. Each completed check uses one credit."
    • changedInput schema / required
      Previous value: -[
-  "question",
-  "apiKey"
-]New value: +[
+  "question"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / apiKey / description
      Previous value: -"Your Oathlayer API key from your dashboard at oathlayer.com."New value: +"Your Oathlayer API key from oathlayer.com. Each completed check uses one credit."
    • changedInput schema / properties / question / description
      Previous value: -"The question or statement you want Oathlayer to verify."New value: +"The question to verify, in plain words (for a legal citation, include the full case name and citation). Spanish questions are supported."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing cost mechanics ('one credit per completed check; errors and wrong keys cost nothing'), the auth requirement ('Requires an API key from oathlayer.com'), the full tag/state taxonomy with colors, and a scope caveat ('does not judge right or wrong'). The annotations cover safety and openness, but the credit and key behavior could not be inferred from them.

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?

Front-loaded with the trigger condition, which is the right priority, and the tag taxonomy and output layout earn their space given there is no output schema. Minor waste remains: the 'Oathlayer:' trigger is stated twice in near-identical language, and the color list adds length of marginal decision value.

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?

With no output schema, the description carries the full burden of describing return values and does so thoroughly — state, tag message, color, doc ID, plus the separate citation tags and short labels. Auth, cost, and the required response layout are all present, so an agent can both call and report correctly.

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 100%, so both parameters are already documented in structured form. The description adds only light framing around which question to submit ('check the question that follows' the prefix), which does not meaningfully extend the schema's own guidance on question content or the legal-citation format.

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?

States a specific verb and resource: 'Verify an AI answer against real sources', and spells out what comes back (answer, state, tag, color, permanent doc number). An agent knows exactly what this tool does before opening the schema, and there are no siblings to disambiguate from.

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?

Gives an explicit, unambiguous trigger ('when the user message starts with Oathlayer:') including capitalization variants, plus an explicit prohibition: 'even if you already know the answer... do not answer it yourself.' The trigger condition is restated near the end, leaving nothing to inference.

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

All oathlayer toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources