Skip to main content
Glama

List the services verticals

list_verticals
Read-onlyIdempotent

The services verticals Frontier Desk writes a page for: what a data licence looks like in that line of work, the shape of firm each page illustrates, and what decides whether a firm in it may license at all. Pass a key from here to get_vertical. Each page's example card is an illustration, labelled as one; no dollar figure is ever stored on a vertical.

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_verticals"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description adds genuinely non-obvious data caveats: example cards are illustrations and explicitly labelled as such, and no dollar figure is ever stored on a vertical — both prevent an agent from presenting fabricated pricing. It stops short of describing the response fields, but the caveat content is real value beyond the annotations.

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 actionable instruction ('pass a key to get_vertical') and the caveats are worthwhile, but the first sentence is a long triple-clause list of page contents that reads as prose about editorial scope rather than tool behavior. It is informative yet front-loads background over the operation, so a reader must work to extract the call semantics.

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?

For a zero-parameter listing tool with no output schema and strong annotation coverage, the description supplies the essentials: what the items are, that keys feed get_vertical, and the illustration/no-price caveat. Only a hint at the actual shape of a returned entry is missing, which is a minor gap given the simplicity of the call.

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?

Zero parameters, so there is nothing for the description to disambiguate and the baseline applies. It still contributes by telling the caller that the output keys are meant to be fed into get_vertical, which gives the returned identifiers a purpose the empty schema cannot convey.

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 — 'the services verticals Frontier Desk writes a page for' — and sketches what each vertical covers (licence norms, firm shape, licensing eligibility). It is clearly a listing tool distinct from the get_* siblings, though the opening clause is dense enough that the core action ('list these') has to be inferred from the name rather than stated outright.

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 explicitly routes the agent forward: 'Pass a key from here to get_vertical' tells you this is the enumeration step and get_vertical is the detail step. There is no statement of when not to use it or what a caller might do instead if they already know the vertical, so it falls 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