CIA Diagnose

case_studies

Read-onlyIdempotent

Demonstrate real business transformations with before/after metrics. Filter by industry or improvement dimension to validate ROI and see proven solutions for revenue leaks.

Instructions

Show before/after transformation stories from real implementations.

Social proof is the most powerful sales tool. These cases show what's possible when businesses address their revenue leaks.

Use AFTER roi_projector to validate the numbers with real stories.

Args: industry: Filter by industry (optional). dimension: Filter by dimension improved (optional). lang: Language ('es' or 'en').

Returns: dict: Case studies with before/after metrics, timeline, tools used, and ROI achieved.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "case_studies"
  }
}

Input Schema

Name	Required	Default
`lang`	No	es
`industry`	No
`dimension`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Jun 24, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. Description adds valuable behavioral context: returns case studies with before/after metrics, timeline, tools, and ROI. No contradictions with annotations.

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

Conciseness4/5

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

Front-loaded with main purpose, structured with Args/Returns. One persuasive sentence ('Social proof is the most powerful sales tool.') is mildly extraneous but does not detract significantly.

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?

Covers purpose, return fields, and usage context with roi_projector. For a simple read-only list tool with optional parameters and output schema, it is sufficiently complete.

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 0%, so description compensates by explaining each parameter: industry filter, dimension filter, language (es/en). Adds meaning beyond schema titles and defaults.

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 starts with a clear verb and resource: 'Show before/after transformation stories from real implementations.' It distinguishes case_studies from siblings like roi_projector (projection) and business_diagnose (diagnosis) by focusing on real stories with metrics.

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?

Explicitly advises using roi_projector before this tool to validate numbers, providing a usage sequence. However, it lacks explicit when-not-to-use guidance or comparison to other siblings.

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

Deploy Server