Skip to main content
Glama
Sign In

DavisStirling

by org.davisstirling
OverviewDiscussionsAdmin

Get related authorities

get_related_authorities
Read-onlyIdempotent

Use this when you need what a section or case is connected to: sections it cites or that cite it, defined terms it relies on, procedural steps before and after it, and cases that cite it or that it cites. Every connection carries the verbatim text that creates it. Do not use it to find topically similar law; it returns only these fixed connection types.

Input Schema

NameRequiredDescriptionDefault
kindsNoConnection types to return (default all).
limitNoConnections per type (default 10).
authorityYesA section ("4920", "Civ. Code § 4920") or a case (name, citation like "8 Cal.4th 361", or id).

Output Schema

NameRequiredDescriptionDefault
metaYes
authorityYes
truncatedYes
connectionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / connections / items / properties / why / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "layer": {
-        "const": "davisstirling",
-        "type": "string"
-      },
-      "method": {
-        "enum": [
-          "derived",
-          "editorial.human",
-          "editorial.machine-reviewed",
-          "editorial.human-reviewed",
-          "editorial.sourced"
-        ],
-        "type": "string"
-      },
-      "value": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "value",
-      "layer",
-      "method"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "layer": {
+        "const": "davisstirling",
+        "type": "string"
+      },
+      "method": {
+        "enum": [
+          "derived",
+          "editorial.human",
+          "editorial.machine-drafted",
+          "editorial.machine-reviewed",
+          "editorial.human-reviewed",
+          "editorial.sourced"
+        ],
+        "type": "string"
+      },
+      "value": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "value",
+      "layer",
+      "method"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Changed4 schema fields changed
    • addedInput schema / properties / authority / anyOf
      Added value: +[
+  {
+    "maxLength": 200,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "exclusiveMinimum": 0,
+    "type": "number"
+  }
+]
    • removedInput schema / properties / authority / maxLength
      Removed value: -200
    • removedInput schema / properties / authority / minLength
      Removed value: -1
    • removedInput schema / properties / authority / type
      Removed value: -"string"
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuine behavioral context beyond annotations: every connection includes the verbatim source text, and results are limited to a fixed set of connection types. It doesn't discuss pagination or result volume, but the added context is substantive.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the usage condition, then the return semantics, then the exclusion. No filler; every clause carries information.

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?

An output schema exists so return values needn't be explained, and the description fully covers purpose, scope, connection types, and usage boundaries. An agent has everything needed to invoke it correctly.

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, but the description goes further by explaining in prose what the enum values mean (e.g., 'defined terms it relies on' maps to defines_term, 'procedural steps before and after' to precedes/follows). The limit parameter is not addressed, keeping it below a 5.

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 ('what a section or case is connected to') and enumerates the concrete connection types returned (citations, defined terms, procedural steps, citing cases). It clearly distinguishes itself from siblings like find_interpreting_cases and search by naming the exact relationship classes it covers.

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?

Opens with an explicit when-to-use condition and adds a clear when-not-to-use ('Do not use it to find topically similar law'), which routes the agent to search-style siblings. Both the triggering scenario and the exclusion are stated directly.

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

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