Skip to main content
Glama

Read one services vertical

get_vertical
Read-onlyIdempotent

One services vertical in full: the example firm it illustrates (headcount band, the tools such a firm runs on, how far its records go back, and the routes worth weighing), what changes in that line of work, and what decides whether a firm in it may license at all. The card is an illustration and says so in evidence. Figures for a real company come from instant_range, which quotes each buyer program's own published page.

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": {
      "vertical": "<vertical>"
    },
    "name": "get_vertical"
  }
}

Input Schema

NameRequiredDescriptionDefault
verticalYesThe vertical's key, as list_verticals gives it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful caveat beyond that — the card is an illustration and flags itself in `evidence`, warning the agent not to treat values as real firm data. It says nothing about behavior for an invalid key or about the shape of the returned object.

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

Conciseness3/5

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

The core statement is front-loaded, but the sentence is long and hyphenated with a nested parenthetical inventory, and phrases like 'the routes worth weighing' are evocative rather than informative. It could convey the same content in roughly half the words.

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 carries the burden of describing return content, and it does so by enumerating the fields the card exposes plus the `evidence` flag. Annotations handle the safety profile; the only remaining gap is error behavior for an unknown vertical key.

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 `vertical` parameter is documented in-schema with length constraints. The description reinforces where the key comes from (list_verticals) but adds no format, casing or normalization detail beyond the schema, 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 names a specific resource (one services vertical) and enumerates what it contains: an illustrative example firm with headcount band, tools, records history and routes, plus what changes in the line of work and licensing determinants. It implicitly separates itself from list_verticals (key source) and instant_range (real company figures), though the verb 'read one' comes largely from the title rather than the description.

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 gives clear routing context: use list_verticals to obtain the key, and use instant_range for figures on a real company rather than this illustrative card. It does not state explicit exclusions or preconditions for calling this tool, so it stops short of full when/when-not guidance.

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