LegalAIMCP Directory

Search legal AI tools

search_legal_ai_tools

Read-onlyIdempotent

Search the legalaimcp.com directory of AI tools and MCP servers built for law firms. Filter by free-text query, practice-area category, and pricing model. Use this when someone asks what AI tooling exists for legal work such as contract review, legal research, client intake, billing, or compliance.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return (1–25, default 10)
`query`	No	Free-text search over tool names, taglines, and descriptions, e.g. "contract review"
`pricing`	No	Pricing-model filter: free, freemium, paid, or contact
`category`	No	Practice-area filter — get slugs from list_legal_ai_categories

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes	Number of tools returned
`tools`	Yes	Matching tools, link-verified listings first

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedJul 29, 2026

changedInput schema / properties / category / description

Previous value: -"Practice area filter"New value: +"Practice-area filter — get slugs from list_legal_ai_categories"

addedInput schema / properties / limit / description

Added value: +"Maximum number of results to return (1–25, default 10)"

changedInput schema / properties / pricing / description

Previous value: -"Pricing model filter"New value: +"Pricing-model filter: free, freemium, paid, or contact"

changedInput schema / properties / query / description

Previous value: -"Free-text search over tool names and taglines, e.g. \"contract review\""New value: +"Free-text search over tool names, taglines, and descriptions, e.g. \"contract review\""

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "description": "Number of tools returned",
+      "type": "number"
+    },
+    "tools": {
+      "description": "Matching tools, link-verified listings first",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "category": {
+            "description": "Practice-area category slug",
+            "type": "string"
+          },
+          "category_label": {
+            "description": "Human-readable category name",
+            "type": "string"
+          },
+          "install_command": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "MCP install command, if the tool ships an MCP server"
+          },
+          "links_verified": {
+            "description": "True if an automated check confirmed every URL on this listing resolved, as of links_verified_at. An automated link check only — NOT an endorsement, security audit, or legal review.",
+            "type": "boolean"
+          },
+          "links_verified_at": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "ISO date of the last passing link check; null = not confirmed (often just bot-blocking)"
+          },
+          "listing_url": {
+            "description": "Canonical listing page on legalaimcp.com",
+            "type": "string"
+          },
+          "maker": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Creator or vendor name"
+          },
+          "name": {
+            "description": "Tool name",
+            "type": "string"
+          },
+          "pricing_details": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Pricing notes, if any"
+          },
+          "pricing_model": {
+            "description": "One of: free, freemium, paid, contact",
+            "type": "string"
+          },
+          "repo": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Source repository, if open source"
+          },
+          "slug": {
+            "description": "Stable listing identifier — pass to get_legal_ai_tool",
+            "type": "string"
+          },
+          "tagline": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "One-line summary"
+          },
+          "website": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Tool website"
+          }
+        },
+        "required": [
+          "slug",
+          "name",
+          "tagline",
+          "category",
+          "category_label",
+          "pricing_model",
+          "pricing_details",
+          "links_verified",
+          "links_verified_at",
+          "website",
+          "repo",
+          "install_command",
+          "maker",
+          "listing_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "tools"
+  ],
+  "type": "object"
+}

First observedJul 28, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, idempotent read operation. The description adds that results can be filtered by query, category, and pricing, but does not disclose any additional behavioral traits beyond what the annotations and schema already convey.

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?

The description is two sentences long, front-loaded with the core purpose, and uses specific examples. Every word adds value; there is no fluff or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema and comprehensive annotations, the description covers the essential purpose and filtering capabilities. It could be slightly improved by hinting at pagination or response structure, but the output schema likely handles that. The description is complete enough for effective use.

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 description coverage is 100%, so the baseline is 3. The description lists the three filter types (free-text, category, pricing), which mirrors the schema's descriptions without adding new meaning or usage nuances. No extra value is provided beyond what the parameter descriptions already offer.

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 it searches the legalaimcp.com directory for AI tools and MCP servers, with specific filter dimensions (free-text, category, pricing). It includes concrete examples like 'contract review' and distinguishes from sibling tools by implying that get_legal_ai_tool retrieves a single tool and list_legal_ai_categories returns category slugs.

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 explicitly says 'Use this when someone asks what AI tooling exists for legal work...', providing clear context. However, it does not explicitly state when not to use it or contrast with siblings beyond the implicit differentiation, which would improve the score to 5.

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

All LegalAIMCP Directory 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?