Skip to main content
Glama

Stratalize Intelligence

Get Healthcare Category Intelligence

get_healthcare_category_intelligence
Read-only

Use when researching which vendors dominate AI recommendations in a healthcare technology category or validating a health IT vendor selection. Returns top recommended vendors, AI consensus narrative, and sample size from healthcare-specific citation analysis. Example: EHR category — Epic leads at 67% AI citation share, Oracle Health 18%, MEDITECH 9% — consensus near-universal for large health systems, fragmenting below 200 beds. Source: Stratalize AI citation composite. $0.10 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>"
    },
    "name": "get_healthcare_category_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses data provenance ('Stratalize AI citation composite'), the unit cost ('$0.10 USDC per call'), and the shape of the return (top vendors, consensus narrative, sample size). The worked EHR example with real share percentages shows an agent what the output looks like and how consensus varies by segment, which the annotations cannot convey.

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?

The trigger is front-loaded in the first clause, followed by return contents and then evidence. The illustrative Epic/Oracle/MEDITECH example is long for a description but does real work in establishing output shape; only the segment-level detail ('fragmenting below 200 beds') is borderline expendable.

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?

With no output schema, the description correctly carries the return-value burden by enumerating the three result components, and it adds cost and source information an agent needs before paying for a call. The one gap is that the required 'category' input's acceptable format is never pinned down.

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 description coverage is 0% for the single required 'category' parameter, so the schema contributes no meaning. The description partially compensates by showing an example value ('EHR category') and by tying the category to healthcare technology, but it never states the expected granularity or format, leaving that inference to the agent.

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 uses a concrete verb and resource ('Returns top recommended vendors, AI consensus narrative, and sample size from healthcare-specific citation analysis') and constrains scope to healthcare technology categories and health IT vendor selection. That healthcare-specific framing distinguishes it from the broader category-level siblings, so an agent can tell what this tool uniquely produces without opening the schema.

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?

It opens with an explicit trigger: 'Use when researching which vendors dominate AI recommendations in a healthcare technology category or validating a health IT vendor selection.' That is clear when-to-use guidance, but there is no when-not guidance and no sibling is named as the alternative for non-healthcare categories.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources