Meta Council

Ask Legal

ask_legal

Read-onlyIdempotent

Request fixed legacy Themis source/citation records and attach a proposed Laws & Regulations agent/source/synthesis plan whose routes are planned_not_run. Check the law uses fixed legacy provider-record retrieval, but returned records do not prove exact citation identity, relevance, authority, or corpus coverage. Generated research requires authentication, exact THEMIS_NEUTRAL_SCHEMA_VERSION=themis_neutral_research/v1, the operator gate, a verified authenticated corpus manifest, and an atomic spend reservation. The manifest verifier is not available yet, so generated mode remains disabled. Provider assertions/gaps are enum codes linked to evidence whose quote-fidelity state is provider-reported and rendered with fixed server text; any legacy verdict or answer prose is withheld. Returns legal_evidence_graph/v1. Automated research only, not legal advice. Requires legal:run.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`context`	No	Optional factual context; treated as unverified input. The normalized question plus context must fit 2,000 characters total.
`domains`	No	Optional domain hints such as OSHA, building_codes, or sports_regulation.
`quality`	No	Policy for proposed, unexecuted model-quality and reasoning-effort routes.	balanced
`question`	Yes	Laws or regulations research question (no credentials or secrets). After normalized context is appended, the combined provider question must fit 2,000 characters.
`jurisdiction`	No	Request hint forwarded to the legacy provider; it does not prove corpus coverage.	auto
`max_sections`	No	Optional maximum number of provider-returned source/citation records.
`research_mode`	No	Fixed legacy provider-record retrieval or an explicit request for fail-closed, neutral Themis generation.	check_law
`model_overrides`	No	Optional model-id overrides for proposed, unexecuted agent routes.
`requested_agents`	No	Up to seven catalog agent additions for the proposed plan; one of the eight total agent slots is reserved for its baseline agent.
`reasoning_effort_overrides`	No	Optional effort overrides for proposed, unexecuted agent routes.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "text": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "text"
-  ],
-  "type": "object"
-}New value: +null

Changed5 schema fields changedAug 13, 2026

changedInput schema / properties / context / description

Previous value: -"Optional factual context; treated as unverified input."New value: +"Optional factual context; treated as unverified input. The normalized question plus context must fit 2,000 characters total."

changedInput schema / properties / jurisdiction / description

Previous value: -"Corpus jurisdiction filter."New value: +"Request hint forwarded to the legacy provider; it does not prove corpus coverage."

changedInput schema / properties / max_sections / description

Previous value: -"Optional maximum number of supporting sections."New value: +"Optional maximum number of provider-returned source/citation records."

changedInput schema / properties / question / description

Previous value: -"Laws or regulations research question (no credentials or secrets)."New value: +"Laws or regulations research question (no credentials or secrets). After normalized context is appended, the combined provider question must fit 2,000 characters."

changedInput schema / properties / research_mode / description

Previous value: -"Source-first retrieval or an explicit request for fail-closed, neutral Themis generation."New value: +"Fixed legacy provider-record retrieval or an explicit request for fail-closed, neutral Themis generation."

Changed8 schema fields changedAug 8, 2026

addedInput schema / properties / context

Added value: +{
+  "default": "",
+  "description": "Optional factual context; treated as unverified input.",
+  "maxLength": 2000,
+  "type": "string"
+}

addedInput schema / properties / domains

Added value: +{
+  "default": [],
+  "description": "Optional domain hints such as OSHA, building_codes, or sports_regulation.",
+  "items": {
+    "maxLength": 80,
+    "type": "string"
+  },
+  "maxItems": 8,
+  "type": "array"
+}

addedInput schema / properties / model_overrides

Added value: +{
+  "additionalProperties": {
+    "maxLength": 160,
+    "minLength": 1,
+    "type": "string"
+  },
+  "default": {},
+  "description": "Optional model-id overrides for proposed, unexecuted agent routes.",
+  "maxProperties": 8,
+  "propertyNames": {
+    "maxLength": 80,
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "object"
+}

addedInput schema / properties / quality

Added value: +{
+  "default": "balanced",
+  "description": "Policy for proposed, unexecuted model-quality and reasoning-effort routes.",
+  "enum": [
+    "fast",
+    "balanced",
+    "deep"
+  ],
+  "type": "string"
+}

changedInput schema / properties / question / description

Previous value: -"Legal research question (no credentials or secrets)."New value: +"Laws or regulations research question (no credentials or secrets)."

addedInput schema / properties / reasoning_effort_overrides

Added value: +{
+  "additionalProperties": {
+    "enum": [
+      "low",
+      "medium",
+      "high",
+      "max"
+    ],
+    "type": "string"
+  },
+  "default": {},
+  "description": "Optional effort overrides for proposed, unexecuted agent routes.",
+  "maxProperties": 8,
+  "propertyNames": {
+    "maxLength": 80,
+    "minLength": 1,
+    "type": "string"
+  },
+  "type": "object"
+}

addedInput schema / properties / requested_agents

Added value: +{
+  "default": [],
+  "description": "Up to seven catalog agent additions for the proposed plan; one of the eight total agent slots is reserved for its baseline agent.",
+  "items": {
+    "maxLength": 80,
+    "type": "string"
+  },
+  "maxItems": 7,
+  "type": "array"
+}

addedInput schema / properties / research_mode

Added value: +{
+  "default": "check_law",
+  "description": "Source-first retrieval or an explicit request for fail-closed, neutral Themis generation.",
+  "enum": [
+    "check_law",
+    "themis"
+  ],
+  "type": "string"
+}

AddedJul 22, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The description goes substantially beyond the annotations. It discloses the return type ('legal_evidence_graph/v1'), the requirement for authentication and specific schema version, the disabled generated mode, the withholding of verdict prose, and the 'fixed server text' rendering of provider assertions. It also notes the atomic spend reservation and operator gate. These are non-obvious behaviors that an agent needs to know, adding significant value over the readOnlyHint and idempotentHint annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph with multiple clauses and technical jargon (e.g., 'THEMIS_NEUTRAL_SCHEMA_VERSION', 'atomic spend reservation', 'enum codes linked to evidence'). While informative, it lacks structure (no bullets or sections) and is not front-loaded for readability. It could be broken into shorter sentences or bullet points for easier parsing by an agent, making it less concise than optimal.

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?

Given the tool's complexity (10 params, no output schema, nested objects, authentication needs), the description is remarkably complete. It covers the return type, the disabled mode, permission requirements, safety caveats, and provider fidelity limitations. An agent would have enough context to call the tool correctly and interpret results, even without an output schema. This is a comprehensive definition.

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?

The input schema provides 100% coverage with detailed descriptions for each parameter (e.g., question max length, domains enum, quality default). The tool description does not repeat or add much parameter-specific meaning; it mainly describes overall behavior (e.g., request records, attach plan) rather than clarifying individual parameters. Baseline of 3 applies because schema already carries the descriptive load, and the description adds marginal value here.

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 clearly states the tool's function: requesting legacy Themis source/citation records and attaching a proposed research plan. It specifies the resource (Themis records) and the action (request and attach). It also mentions 'Check the law uses fixed legacy provider-record retrieval,' reinforcing the purpose. No sibling tool serves this legal-research function, so it stands apart distinctly.

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?

The description provides context on when this tool is usable (requires 'legal:run' permission) and when it is not (generated mode disabled due to missing manifest verifier). It also clarifies limitations ('Automated research only, not legal advice'), which guides appropriate use. However, it does not explicitly mention alternative tools or exclusion criteria because no direct sibling exists; the guidance is indirect but sufficient.

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

All Meta Council tools Inspect

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

Need Help?