case-studies
Server Details
Search DataArt case studies by technology, industry, service, or keyword.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: search_cases finds cases, get_case retrieves full content for a specific case, and get_case_tags lists filtering tags. Descriptions explicitly cross-reference each other, reducing any risk of misselection.
All tool names use consistent snake_case with predictable verb_noun patterns: get_case, get_case_tags, and search_cases. The get_case_tags variation is a natural read-only subresource naming choice and remains readable.
Three tools are well-scoped for a read-only case-studies server: discovery via search, tag discovery for filtering, and full-content retrieval. Each tool earns its place without redundancy.
The surface covers the core lifecycle for browsing case studies: browse all via empty query, search by text and tags with pagination, discover tags, and fetch full case content by id, slug, or url. No obvious read-only operations are missing for the stated purpose.
Available Tools
3 toolsget_caseGet a DataArt case studyARead-onlyInspect
Get the full content of one case study (article text, challenge, solution, conclusion). The texts are Markdown. Pass the id, slug or url returned by search_cases.
Inputs: idOrSlug (required).
get_case_tagsList DataArt case study filtersARead-onlyInspect
Get all available tags that can be used to filter case studies. Returns a list of tags with id, parentId, and title. The list is flat: parentId is always null. Use the tag ids in the search_cases tagIds parameter.
Inputs: no named parameters.
search_casesSearch DataArt case studiesARead-onlyInspect
Search DataArt case studies by text query and/or tag IDs with pagination. The query can be keywords or a whole question: it is split into words, common words are ignored, whole words are matched in the title, description and tag names (British/American spelling and plurals are folded). Cases containing every word come first (allTermsTotal of them), then cases containing some of the words, best match first. Pass an empty query to browse all cases. Use get_case_tags to discover available tag IDs before filtering. Text and tags combine with AND. Multiple tags combine per tagMatch: "any" (default) or "all". Returns short records; use get_case with the id, slug or url of a result to get its full text.
Inputs: query (required), page, tagIds, pageSize, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Search 1,000+ practical AI use cases by industry and workflow, with AI consulting services.
Search 400k+ SaaS and software companies by category, technology, country, pricing, and more.
Global AI product engineering partner: services, case studies, fit check, booking
Send a software project enquiry to Order Group and browse its case studies (fintech, energy, IoT).
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search and read 1,300+ real-world case studies from company engineering blogs, papers, and talks on A/B testing, causal inference, recommendation, search, fraud, forecasting, ML, and LLM-in-analytics problems, returning problems, solutions, tools, and links to originals.1MIT
- AlicenseAqualityCmaintenanceSearch 200M+ patents and scientific literature in natural language using PatSnap's global R&D intelligence database.286Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables retrieval of structured architectural case study data for design research, supporting case browsing, filtering, and downloadable research packages through natural language.20 npmMIT

Patsnap-mcpofficial
AlicenseNot gradedqualityCmaintenanceSearch 1B+ biological sequences, antibodies, and multi-omics data via specialized bio-intelligence tools.70Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.