Skip to main content
Glama
cirwel

UNITARES

by cirwel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

consult

Request model advice on a question or material with configurable privacy, effort, and purpose for advisory input without a review record.

Instructions

Ask a model for advice, no review record; effort='thorough' needs cloud privacy and an operator extension; on-record: request_review.

Input Schema

NameRequiredDescriptionDefault
briefYesQuestion or material to send for advisory model help.
modelNoStandard lane: a model ollama:local lists.
effortNoOmit: thorough for a CLI host_id or host_ids, else standard. Explicit effort must match.
host_idNoPin a host; omitted effort follows it. External needs cloud_allowed; no fallback.
privacyNolocal confines routing to the configured local inference service; cloud_allowed permits, but does not require, external processing.local
purposeNoDesired advisory operation. critique remains model advice, not a governed peer-review verdict.answer
agent_idNoUUID; leave unset for yourself.
host_idsNoCouncil of 2-3 CLI hosts; needs cloud_allowed.
response_modeNocompact returns the advisory result and policy outcome; full adds a single diagnostics object with route and inference provenance.compact
allow_degradedNoAllow thorough effort to fall back to standard local inference. This never weakens the requested privacy policy.
continuity_tokenNoSame-process rebind proof only; never a cross-process resume.
client_session_idNoBinding id for calls in this process; not a cross-process proof.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.5.0
    • addedInput schema / properties / model
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 200,
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Standard lane: a model ollama:local lists."
+}
  2. Changed4 schema fields changedv3.4.0
    • removedInput schema / properties / effort / default
      Removed value: -"standard"
    • changedInput schema / properties / effort / description
      Previous value: -"standard uses the lower-overhead inference lane; thorough requests the operator-authorized strong-model lane."New value: +"Omit: thorough for a CLI host_id or host_ids, else standard. Explicit effort must match."
    • addedInput schema / properties / host_id
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 128,
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Pin a host; omitted effort follows it. External needs cloud_allowed; no fallback."
+}
    • addedInput schema / properties / host_ids
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Council of 2-3 CLI hosts; needs cloud_allowed."
+}
  3. Changed3 schema fields changedv3.1.0
    • changedInput schema / properties / agent_id / description
      Previous value: -"UNIQUE agent identifier; optional when session-bound (auto-injected)."New value: +"UUID; leave unset for yourself."
    • changedInput schema / properties / client_session_id / description
      Previous value: -"In-session binding id from start_session()/identity(); pass it on same-process calls. Not a cross-process proof."New value: +"Binding id for calls in this process; not a cross-process proof."
    • changedInput schema / properties / continuity_token / description
      Previous value: -"Ownership proof from onboard()/identity(), for same-live-process rebinds only. Not a cross-process resume credential."New value: +"Same-process rebind proof only; never a cross-process resume."
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true and non-idempotent, and the description adds context the annotations cannot: no review record is produced, and 'thorough' effort requires cloud privacy plus an operator extension, i.e. a real prerequisite that can block the call. It stops short of stating cost, latency or failure behavior.

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?

Two clauses, front-loaded with the action and the key exclusion; nothing is padding. The compression costs some readability – semicolon-separated policy fragments read like notes rather than a sentence – but no information is wasted.

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?

For a 12-parameter tool with no output schema, the description covers the pivotal routing and precondition but says nothing about what comes back (response_mode, continuity_token semantics, degraded fallback behavior) beyond what the schema already documents. Adequate, not thorough.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description earns above baseline by disclosing the cross-parameter constraint (thorough effort needs cloud privacy enabled and an operator extension) that the per-parameter enum descriptions only partially imply.

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?

States a concrete verb+resource ('Ask a model for advice') and immediately scopes it with 'no review record', which tells the agent this is an advisory, non-governed consultation. It does not name a near-identical sibling beyond request_review, and the phrasing is telegraphic, but the core action is unambiguous.

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?

Explicitly routes the agent: use this for untracked advice, use request_review when the interaction must be on-record. The alternative and its selection condition are stated, though 'no review record' is compressed enough that the contrast requires a second read.

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

Deploy Server

Other Tools