Skip to main content
Glama

Raziel

by io.github.tide-foundation
OverviewDiscussionsAdmin

tide_hosting

Read-only

Where TideCloak runs: local Docker vs partner-hosted (Skycloak managed TideCloak-as-a-service). Returns the local-vs-hosted decision with the honest trade-offs, the trust model, the verified Skycloak API reference (correct cluster field names and the required version), and the full provisioning playbook. CALL THIS BEFORE STARTING ANY TIDECLOAK DEPLOYMENT — the choice must be made up front (I-17) because a realm cannot be moved between local and hosted afterwards. Triggers: 'deploy to production', 'deploy TideCloak', 'go live', 'host this somewhere', 'managed option', 'stable URL', 'can someone host TideCloak for us', or any request to stand up an instance where local-vs-hosted has not been settled.

Input Schema

NameRequiredDescriptionDefault
partNoWhich part to return when the document is delivered in several parts. Omit for part 1; the response says how many there are.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / part
      Added value: +{
+  "description": "Which part to return when the document is delivered in several parts. Omit for part 1; the response says how many there are.",
+  "minimum": 1,
+  "type": "integer"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing the content returned and the downstream irreversibility constraint (a realm cannot be moved after choosing), which is the behavioral stake that matters for sequencing.

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 core decision and efficiently structured around purpose, rationale, and triggers. Slightly long trigger enumeration, but each line earns its place by widening match surface for a high-stakes pre-deployment call.

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?

No output schema exists, so the description carries the return burden — and it does, naming trade-offs, trust model, API reference, and playbook. For a read-only single-param document tool, nothing needed to call it correctly is missing.

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?

Only one parameter ('part') exists and its schema description coverage is 100%, so the schema fully documents it. The description adds no meaning beyond that, so the baseline 3 applies.

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 the exact decision the tool serves — local Docker vs partner-hosted TideCloak — and enumerates the payload (trade-offs, trust model, Skycloak API reference, provisioning playbook). An agent can distinguish this from generic siblings like tide_playbook or tide_choose_scenario without opening any schema.

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 imperative ('CALL THIS BEFORE STARTING ANY TIDECLOAK DEPLOYMENT'), the reason ('the choice must be made up front (I-17) because a realm cannot be moved between local and hosted afterwards'), a trigger list, and the condition that selects it ('where local-vs-hosted has not been settled'). Routing is unambiguous.

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

All Raziel 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