Search a curated directory of AI tools and MCP servers for law firms. Read-only, free, no auth.
Scored across 4 tools
Each tool has a distinct role: search (discovery/list), get (detail on a known slug), list_categories (orientation), and recommend (ranked fit). Descriptions explicitly resolve the only potential overlap by telling the agent when to use recommend instead of search.
All four tools follow a consistent verb_noun snake_case pattern (get_legal_ai_tool, list_legal_ai_categories, recommend_legal_ai_tools, search_legal_ai_tools). The prefixing is uniform and predictable.
Four tools is a tight, well-scoped set for a read-only directory: browse, search, detail, and recommend. It is on the lean side, but each tool earns its place with no filler.
The read-only discovery lifecycle (orient, search, detail, recommend) is fully covered, so no dead ends for the core use case. Minor gaps like browsing all tools without a query or comparing multiple tools are workarounds, not blockers.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Listing slug, e.g. "harvey-ai" — taken from a search result |
| Name | Required | Description |
|---|---|---|
| tool | No | The listing, present when found is true |
| found | Yes | False when no published listing has this slug |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety and determinism profile is fully covered. The description adds only a note about what the listing includes (description text, install command), which is largely output content already covered by the output schema. It does not mention behavior for an unknown or stale slug.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences with zero filler: the first defines the operation and its return payload, the second defines the workflow trigger. Information is front-loaded and every clause earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With one required parameter, full schema coverage, rich annotations and an output schema, the description covers everything an agent needs to select and invoke the tool. The only unaddressed gap is failure behavior for a nonexistent slug, which is minor given the low complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%: the slug parameter already documents format, pattern, max length and provenance ('taken from a search result'). The description's 'by its slug' and 'after search_legal_ai_tools' restate that provenance without adding syntax or edge-case guidance, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Get the full listing for one legal AI tool by its slug') and enumerates what the listing contains (complete description, MCP install command). It is clearly the detail-lookup counterpart to search_legal_ai_tools, so an agent can distinguish it from all siblings without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly positions the tool in a workflow: 'Use after search_legal_ai_tools to go deeper on a specific result,' naming the alternative and the condition that selects this one. It stops short of saying when not to use it (e.g. for browsing or listing), so it falls just below the top band.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
List the practice-area categories in the legalaimcp.com directory, with how many published tools each contains. Useful for orienting before a search.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
| total | Yes | Total published tools in the directory |
| categories | Yes | All practice-area categories |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety and idempotency are clear. The description adds that it lists categories with counts, consistent with annotations. No contradictions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the main action, no waste. Every word contributes to clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and an output schema, the description fully explains what the tool returns (categories with counts). No gaps for the intended use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, and schema coverage is 100%. Baseline of 4 applies; description adds no param info but none is needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool lists practice-area categories and their tool counts. Differentiates from sibling tools (get_legal_ai_tool and search_legal_ai_tools) by focusing on categories rather than specific tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states 'Useful for orienting before a search,' providing clear context for when to use. While it doesn't contrast with siblings, the usage scenario is clear and sufficient for this simple tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Rank legal AI tools by fit for a specific practice area and firm size, with a score and the matched factors behind it. Use this instead of search_legal_ai_tools when someone describes their firm (e.g. "solo family law practice" or "20-attorney litigation firm") and wants a recommendation, not just a list.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of recommendations to return (1-5, default 5) | |
| firm_size | Yes | Firm size: solo, small (2-10 attorneys), mid (11-50), or large (50+) | |
| practice_area | Yes | Practice-area category slug — get slugs from list_legal_ai_categories |
| Name | Required | Description |
|---|---|---|
| count | Yes | Number of recommendations returned |
| recommendations | Yes | Ranked highest-fit first. Empty when nothing in the directory matched either input. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world, so safety behavior is fully covered. The description adds the output shape (a score plus matched factors), which is mild added value but partly redundant with the output schema. No auth, rate-limit, or ordering/caveat detail is added, so 3 is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences: the first front-loads what the tool produces, the second supplies the routing condition. No filler, no repetition of structured fields.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only ranked-search tool with full schema coverage and an output schema, the description supplies exactly what is missing: the recommendation-vs-list distinction and the input framing. Return values need not be explained since an output schema exists.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and both enums are documented in the schema itself (including the pointer to list_legal_ai_categories for slugs). The description only restates that practice area and firm size drive the ranking, adding no syntax or format meaning beyond the schema, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (rank) plus resource (legal AI tools) and scope (by fit for practice area and firm size), and explicitly names the sibling it is not (search_legal_ai_tools). An agent can distinguish this from search/list/get siblings without inspecting schemas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives an explicit when/when-not: use this instead of search_legal_ai_tools when the user describes their firm and wants a recommendation rather than a list, with concrete examples ('solo family law practice', '20-attorney litigation firm'). Nothing is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 |
| Name | Required | Description |
|---|---|---|
| count | Yes | Number of tools returned |
| tools | Yes | Matching tools, link-verified listings first |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the full safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the agent knows this is a safe, repeatable read. The description adds only that results come from a curated directory, with no rate limits, pagination behavior, or result ordering context beyond what annotations cover.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, front-loaded with what and where before the filter list and the usage trigger. Efficient and readable, with no filler, though the middle filter sentence is largely redundant with the schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 need not be explained, and annotations cover the safety profile. The description is complete enough to invoke correctly; minor gaps are the omitted 'limit' cap and any note on result relevance, which are low-stakes given the rich schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all four parameters (limit, query, pricing, category) are already fully documented with enums and defaults. The description restates which filters exist but adds no syntax, format, or interaction detail beyond the schema; baseline 3 applies when the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Search) and resource (legalaimcp.com directory of AI tools and MCP servers built for law firms), so the agent knows exactly what is being queried. It does not explicitly differentiate itself from siblings like get_legal_ai_tool or recommend_legal_ai_tools, but the directory-search scope is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives a clear trigger: "Use this when someone asks what AI tooling exists for legal work" with concrete examples (contract review, legal research, client intake, billing, compliance). It does not name the alternative siblings or say when NOT to use it (e.g. when a specific tool is already known), so it stops short of full explicit routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
get_legal_ai_tool2 fields changedOutput schema / properties / tool / properties / connectionAdded value: +{
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "customer_account_tested": {
+ "const": false,
+ "type": "boolean"
+ },
+ "documentation_reviewed_at": {
+ "type": "string"
+ },
+ "permissions": {
+ "type": "string"
+ },
+ "requirements": {
+ "type": "string"
+ },
+ "setup": {
+ "type": "string"
+ },
+ "source_url": {
+ "format": "uri",
+ "type": "string"
+ },
+ "type": {
+ "enum": [
+ "official",
+ "community"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "source_url",
+ "documentation_reviewed_at",
+ "requirements",
+ "permissions",
+ "setup",
+ "customer_account_tested"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Reviewed setup documentation, not a compatibility or security test. Null means no reviewed setup guide is attached, not that a connector cannot exist."
+}Output schema / properties / tool / requiredPrevious value: -[
- "slug",
- "name",
- "tagline",
- "category",
- "category_label",
- "pricing_model",
- "pricing_details",
- "links_verified",
- "links_verified_at",
- "website",
- "repo",
- "install_command",
- "maker",
- "listing_url",
- "description"
-]New value: +[
+ "slug",
+ "name",
+ "tagline",
+ "category",
+ "category_label",
+ "pricing_model",
+ "pricing_details",
+ "links_verified",
+ "links_verified_at",
+ "website",
+ "repo",
+ "install_command",
+ "maker",
+ "listing_url",
+ "connection",
+ "description"
+]recommend_legal_ai_tools2 fields changedOutput schema / properties / recommendations / items / properties / connectionAdded value: +{
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "customer_account_tested": {
+ "const": false,
+ "type": "boolean"
+ },
+ "documentation_reviewed_at": {
+ "type": "string"
+ },
+ "permissions": {
+ "type": "string"
+ },
+ "requirements": {
+ "type": "string"
+ },
+ "setup": {
+ "type": "string"
+ },
+ "source_url": {
+ "format": "uri",
+ "type": "string"
+ },
+ "type": {
+ "enum": [
+ "official",
+ "community"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "source_url",
+ "documentation_reviewed_at",
+ "requirements",
+ "permissions",
+ "setup",
+ "customer_account_tested"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Reviewed setup documentation, not a compatibility or security test. Null means no reviewed setup guide is attached, not that a connector cannot exist."
+}Output schema / properties / recommendations / items / requiredPrevious value: -[
- "slug",
- "name",
- "tagline",
- "category",
- "category_label",
- "pricing_model",
- "pricing_details",
- "links_verified",
- "links_verified_at",
- "website",
- "repo",
- "install_command",
- "maker",
- "listing_url",
- "score",
- "matched_factors",
- "pricing_note"
-]New value: +[
+ "slug",
+ "name",
+ "tagline",
+ "category",
+ "category_label",
+ "pricing_model",
+ "pricing_details",
+ "links_verified",
+ "links_verified_at",
+ "website",
+ "repo",
+ "install_command",
+ "maker",
+ "listing_url",
+ "connection",
+ "score",
+ "matched_factors",
+ "pricing_note"
+]search_legal_ai_tools2 fields changedOutput schema / properties / tools / items / properties / connectionAdded value: +{
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "customer_account_tested": {
+ "const": false,
+ "type": "boolean"
+ },
+ "documentation_reviewed_at": {
+ "type": "string"
+ },
+ "permissions": {
+ "type": "string"
+ },
+ "requirements": {
+ "type": "string"
+ },
+ "setup": {
+ "type": "string"
+ },
+ "source_url": {
+ "format": "uri",
+ "type": "string"
+ },
+ "type": {
+ "enum": [
+ "official",
+ "community"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "source_url",
+ "documentation_reviewed_at",
+ "requirements",
+ "permissions",
+ "setup",
+ "customer_account_tested"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Reviewed setup documentation, not a compatibility or security test. Null means no reviewed setup guide is attached, not that a connector cannot exist."
+}Output schema / properties / tools / items / requiredPrevious value: -[
- "slug",
- "name",
- "tagline",
- "category",
- "category_label",
- "pricing_model",
- "pricing_details",
- "links_verified",
- "links_verified_at",
- "website",
- "repo",
- "install_command",
- "maker",
- "listing_url"
-]New value: +[
+ "slug",
+ "name",
+ "tagline",
+ "category",
+ "category_label",
+ "pricing_model",
+ "pricing_details",
+ "links_verified",
+ "links_verified_at",
+ "website",
+ "repo",
+ "install_command",
+ "maker",
+ "listing_url",
+ "connection"
+]recommend_legal_ai_tools2 fields changedOutput schema / properties / recommendations / items / properties / pricing_noteAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "Informational only, never affects rank: paid/contact tiers often bundle dedicated support that a free/freemium pick may not. Ties are broken by cost alone — this lets the requester weigh support separately."
+}Output schema / properties / recommendations / items / requiredPrevious value: -[
- "slug",
- "name",
- "tagline",
- "category",
- "category_label",
- "pricing_model",
- "pricing_details",
- "links_verified",
- "links_verified_at",
- "website",
- "repo",
- "install_command",
- "maker",
- "listing_url",
- "score",
- "matched_factors"
-]New value: +[
+ "slug",
+ "name",
+ "tagline",
+ "category",
+ "category_label",
+ "pricing_model",
+ "pricing_details",
+ "links_verified",
+ "links_verified_at",
+ "website",
+ "repo",
+ "install_command",
+ "maker",
+ "listing_url",
+ "score",
+ "matched_factors",
+ "pricing_note"
+]recommend_legal_ai_toolsget_legal_ai_tool2 fields changedInput schema / properties / slug / descriptionPrevious 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"Output 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"
+}list_legal_ai_categories1 field changedOutput schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "categories": {
+ "description": "All practice-area categories",
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "count": {
+ "description": "Published tools in this category",
+ "type": "number"
+ },
+ "label": {
+ "description": "Human-readable category name",
+ "type": "string"
+ },
+ "slug": {
+ "description": "Pass as `category` to search_legal_ai_tools",
+ "type": "string"
+ }
+ },
+ "required": [
+ "slug",
+ "label",
+ "count"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "total": {
+ "description": "Total published tools in the directory",
+ "type": "number"
+ }
+ },
+ "required": [
+ "total",
+ "categories"
+ ],
+ "type": "object"
+}search_legal_ai_tools5 fields changedInput schema / properties / category / descriptionPrevious value: -"Practice area filter"New value: +"Practice-area filter — get slugs from list_legal_ai_categories"Input schema / properties / limit / descriptionAdded value: +"Maximum number of results to return (1–25, default 10)"Input schema / properties / pricing / descriptionPrevious value: -"Pricing model filter"New value: +"Pricing-model filter: free, freemium, paid, or contact"Input schema / properties / query / descriptionPrevious 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\""Output 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"
+}get_legal_ai_toollist_legal_ai_categoriessearch_legal_ai_toolsSearch 7,500+ MCP servers and agent skills plus 1,500 AI tools. Read-only.
Search a curated directory of AI tools, AI agents and MCP servers by task, pricing and platform.
Search a curated directory of 300+ verified AI agents, MCP servers, and agentic tools.
Search a curated directory of agent tools, MCP servers, APIs, protocols and skills. No auth.
Add one secure layer between your agents and this server.
