Skip to main content
Glama

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.2/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, non-destructive behavior, and the description adds material context beyond them: it names the return contents (top vendors, consensus narrative, sample size), discloses the underlying source (Stratalize AI citation composite), and states a per-call price of $0.10 USDC. Cost and data provenance are exactly the kind of disclosure annotations cannot carry; only freshness or latency of the citation data is missing.

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?

It is front-loaded with the 'Use when' trigger, followed by outputs, a worked example, provenance, and price in that order. The example is long but earns its space by showing both output shape and interpretation; little could be cut without losing signal.

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?

With no output schema, the description still tells the agent what comes back (vendors, consensus narrative, sample size) and gives a concrete illustrative result. For a single-parameter, read-only lookup, that plus the source and pricing covers what an agent needs before calling.

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 'category' parameter, so the description has to compensate. The EHR example does show the expected granularity of a category value, which is genuinely useful, but it never states whether the value must match a fixed taxonomy, is free text, or how to phrase a non-EHR category.

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 states a specific verb and resource ('researching which vendors dominate AI recommendations') scoped to healthcare technology categories, and explicitly frames it as healthcare-specific citation analysis. That scoping distinguishes it from the generic sibling tools such as get_category_ai_leaders and get_top_vendors_by_category without needing to name them.

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?

Two concrete use cases are given up front: researching vendor dominance in an AI-recommendation context and validating a health IT vendor selection. The context is clear, but there is no explicit when-not guidance or named alternative for adjacent questions (e.g., market rate or GPO diligence siblings).

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