Skip to main content
Glama

List the five markets

list_markets
Read-onlyIdempotent

The five markets Frontier Desk maps — services, compute, data, credit and capital — with the relationship graphs drawn in each, the columns each graph runs through, the sectors a caller can pick, and counts of what is drawn. Pass a sector slug from here to get_market_sector for that sector's graphs. The whole-field graphs render at https://www.frontierdesk.ai/markets.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description adds the useful fact that the payload includes counts of what is drawn and the columns each graph runs through, plus where full graphs are rendered. It does not spell out the response object shape, but the annotations cover the safety profile adequately.

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?

Three focused sentences, with the content inventory front-loaded and the routing cue second. The first sentence is long and slightly dense ('the columns each graph runs through'), but no sentence is wasted.

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 return-value burden and does a good job enumerating markets, graphs, columns, sectors, and counts. A little more on the overall response structure for a zero-parameter listing would make it complete.

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?

The tool takes no parameters, so the baseline is 4 and there is nothing for the description to clarify. The mention of sector slugs is correctly framed as an input to a downstream tool, not to this one.

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 names the exact resource (the five markets: services, compute, data, credit, capital) and enumerates the payload components: relationship graphs, their columns, selectable sectors, and counts. It also explicitly contrasts itself with get_market_sector, so an agent can separate the two without opening a 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 gives clear routing guidance: pass a sector slug from this result to get_market_sector for that sector's graphs, and offers the frontierdesk.ai URL as the place whole-field graphs render. It stops short of explicit when-not-to-use conditions, but the overview-vs-sector split is clear in context.

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