LegalAIMCP Directory

Get one legal AI tool

get_legal_ai_tool

Read-onlyIdempotent

Get the full listing for one legal AI tool by its slug, including the complete description and MCP install command. Use after search_legal_ai_tools to go deeper on a specific result.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Listing slug, e.g. "harvey-ai" — taken from a search result

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tool`	No	The listing, present when found is true
`found`	Yes	False when no published listing has this slug

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 29, 2026

changedInput schema / properties / slug / description

Previous value: -"Listing slug, e.g. \"harvey-ai\" — taken from a search result URL"New value: +"Listing slug, e.g. \"harvey-ai\" — taken from a search result"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "found": {
+      "description": "False when no published listing has this slug",
+      "type": "boolean"
+    },
+    "tool": {
+      "additionalProperties": false,
+      "description": "The listing, present when found is true",
+      "properties": {
+        "category": {
+          "description": "Practice-area category slug",
+          "type": "string"
+        },
+        "category_label": {
+          "description": "Human-readable category name",
+          "type": "string"
+        },
+        "description": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "Full listing description"
+        },
+        "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",
+        "description"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "found"
+  ],
+  "type": "object"
+}

First observedJul 28, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds that the tool returns 'complete description and MCP install command', giving concrete behavioral details beyond annotations.

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?

Two short, front-loaded sentences with zero waste. First sentence states purpose, second provides usage context.

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?

For a simple tool with one parameter, high annotation coverage, and an existing output schema, the description provides all necessary context: what the tool does, when to use it, and what the response contains.

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 coverage is 100% with a description for the slug parameter. The description mentions 'by its slug' but does not add significant meaning beyond the schema's explanation and example.

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 verb (Get), resource (legal AI tool), and distinguishing details (by slug, includes complete description and MCP install command). It also explicitly positions itself after search_legal_ai_tools, differentiating from siblings.

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?

The description explicitly says 'Use after search_legal_ai_tools to go deeper on a specific result', providing clear when-to-use guidance and an exclusion for search functionality.

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?