CIA Diagnose

list_industries

Read-onlyIdempotent

Retrieve available industry benchmarks for CIA diagnosis. Each industry offers a calibrated benchmark for deep analysis, with a generic benchmark for others.

Instructions

List available industry benchmarks for CIA diagnosis.

Returns the industries with calibrated benchmarks (Tier 1 = premium, deep analysis). Any other industry works too via the generic benchmark.

Returns: dict: Contains: - industries (list[str]): Available benchmark IDs (e.g. ['construction', 'healthcare', 'agency', ...]) - note_es (str): Spanish explanation - note_en (str): English explanation

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": "list_industries"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Jun 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate readOnly, idempotent, and non-destructive. Description adds behavioral context by explaining the return structure (industries list, Spanish and English notes) and the concept of calibrated vs generic benchmarks, which is helpful 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?

Description is concise with front-loaded purpose followed by return details in a clear, structured manner. Every sentence adds value.

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?

Given the tool's simplicity (no params, output schema exists), the description fully explains what is returned and the differentiation between Tier 1 and generic benchmarks. No gaps.

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?

No parameters exist, so baseline is 4. The description does not need to add parameter information.

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?

Clearly states the tool lists available industry benchmarks for CIA diagnosis, distinguishing between calibrated (Tier 1) and generic. The verb 'list' and resource 'industries with benchmarks' are specific, and the purpose is distinct 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context on what the tool returns (calibrated industries and generic benchmark availability), which implicitly guides when to use it. No explicit alternative or exclusion, but context is sufficient.

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

Deploy Server