Skip to main content
Glama

One sector's relationship graphs

get_market_sector
Read-onlyIdempotent

One sector's relationship graphs: the firms drawn in each column, the relations between them in each side's own words, the roster of who does what, and the lines on what the connections show. Takes a sector slug from list_markets: accounting, insurance, wealth, it, healthcare, staffing, legal, engineering, marketing, logistics, distribution, operators, software, business-services, property, manufacturing, build-out. By default (detail "summary") it answers compactly: per graph, the counts, the columns, the lines on what the connections show, and the first firms and relations in the order the page draws them, each named, with a link to the full JSON. detail "full" answers with the same JSON the /markets page loads when a visitor picks that sector, which can run past 100 KB.

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": {
      "sector": "<sector>"
    },
    "name": "get_market_sector"
  }
}

Input Schema

NameRequiredDescriptionDefault
graphNoOne graph instead of all of them, by key, for example "services" or "credit". Omit for every graph the sector has.
limitNoWith detail "summary": how many firms and relations to name per graph. Default 12.
detailNo"summary" (the default) for counts and the first firms and relations in each graph; "full" for the whole JSON the page loads.summary
sectorYesThe sector to draw: accounting, insurance, wealth, it, healthcare, staffing, legal, engineering, marketing, logistics, distribution, operators, software, business-services, property, manufacturing, build-out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add operational context — and it does: default compact mode, the fact that full returns the same payload the /markets page loads, its >100 KB size, and that summary output follows page draw order with a link to the full JSON. That size and ordering detail is genuinely useful beyond the annotations, though response shape per graph is only loosely sketched.

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 information is front-loaded, but the opening sentence is a long run-on that repeats 'the lines on what the connections show' twice and re-enumerates the full sector slug list already present in the schema. The content earns its place; the phrasing does not.

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 returns and does so for both detail modes, including payload size and ordering. Only minor gaps remain, such as how graph keys relate to the sector's columns and whether summary output is truncated by anything other than limit.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning: it explains what 'summary' actually contains versus 'full', ties full to the page payload, and notes the ordering of returned firms and relations. It largely restates the sector enum and the limit default rather than adding to them, which keeps it from a 5.

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?

States a specific verb and resource — retrieving one sector's relationship graphs — and enumerates exactly what comes back: firms per column, relations in each side's own words, the roster of who does what, and the connection lines. That is enough for an agent to distinguish it from list_markets or get_vertical without opening any 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?

Gives concrete routing context by tying the sector argument to list_markets and by explaining the summary/full trade-off, including the warning that full 'can run past 100 KB'. It stops short of naming an explicit alternative tool or a when-not-to-use condition, so it lands at clear context rather than full routing 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