Skip to main content
Glama

get_industry_insights

Read-onlyIdempotent

Retrieve public market insights and hiring demand for a specific industry vertical by name to assess sector trends and talent needs.

Instructions

Get public market insights and hiring demand for an industry vertical.

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": {
      "ind": "<ind>"
    },
    "name": "get_industry_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
indYesIndustry name or vertical (e.g. 'Technology', 'Healthcare', 'Finance')

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.8
    • addedInput schema / properties / ind / description
      Added value: +"Industry name or vertical (e.g. 'Technology', 'Healthcare', 'Finance')"
  2. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the word "public," which usefully signals non-user-specific, externally sourced data, but says nothing about freshness, coverage, or cost/latency of an open-world lookup.

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?

One front-loaded sentence with zero filler. It is efficient, though the brevity edges toward under-specification given the ambiguity with a sibling tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be explained, and annotations cover the safety profile. The remaining gap is routing: for a tool that overlaps heavily with deep_industry_analysis, the description should say how they differ.

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 coverage is 100% and the single parameter is documented with concrete examples ('Technology', 'Healthcare', 'Finance'). The description's phrase "industry vertical" merely restates the schema, adding no syntax or normalization guidance beyond it, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a clear verb ("Get") with a specific resource ("public market insights and hiring demand for an industry vertical"), so an agent knows exactly what data comes back. It does not, however, distinguish this from the sibling tool deep_industry_analysis, which sounds like the same domain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The presence of deep_industry_analysis among the siblings makes the omission costly — an agent has no basis for choosing between a quick insight lookup and a deep analysis.

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