Skip to main content
Glama

Category leaderboard

board
Read-onlyIdempotent

The top of one category's Substack leaderboard, with each writer's followers, paid band and move since the previous board. board is bestsellers (ranked by paid subscribers, the default) or rising (recent paid growth). category is a slug or name such as technology, business, culture or U.S. Politics; when it does not match, the result lists the closest categories.

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": {
      "category": "<category>"
    },
    "name": "board"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardNobestsellers (default) or rising.
categoryYesA category slug or name, for example technology, us-politics or Food & Drink.

Output Schema

NameRequiredDescriptionDefault
urlYes
rowsYes
slugNo
boardYes
categoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / board / description
      Added value: +"bestsellers (default) or rising."
    • addedInput schema / properties / category / description
      Added value: +"A category slug or name, for example technology, us-politics or Food & Drink."
    • changedInput schema / properties / category / maxLength
      Previous value: -40New value: +60
    • removedInput schema / properties / category / pattern
      Removed value: -"^[a-z0-9-]+$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "board": {
      +      "type": "string"
      +    },
      +    "category": {
      +      "type": "string"
      +    },
      +    "rows": {
      +      "items": {
      +        "properties": {
      +          "followers": {
      +            "anyOf": [
      +              {
      +                "type": "integer"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "handle": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "paid_band": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "previous_rank": {
      +            "anyOf": [
      +              {
      +                "type": "integer"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "publication": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "rank": {
      +            "type": "integer"
      +          },
      +          "recommended_by": {
      +            "anyOf": [
      +              {
      +                "type": "integer"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "slug": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "category",
      +    "board",
      +    "url",
      +    "rows"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds behavior beyond that: the fallback-to-closest-categories behavior on unmatched input and the fact that a 'move since the previous board' is included in the payload. It does not say how many rows constitute 'the top', which is the one remaining behavioral unknown.

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?

Two sentences, no filler, and the resource definition leads before parameter explanation. The second sentence is compressed into a telegraphic 'board is ... or ...' style that reads slightly clipped, but nothing is redundant and every clause carries information.

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?

An output schema exists, so the description is not obliged to enumerate return values, yet it still summarizes them usefully. The mismatch-recovery behavior is the key piece an agent needs and it is present. The only gap is the unstated result size implied by 'the top of' a leaderboard.

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 earns more: it explains that 'bestsellers' is the default and what each board value actually measures (paid subscribers vs. recent paid growth), and it clarifies that category accepts either a slug or a human-readable name, illustrating the mapping with 'U.S. Politics'. The schema only lists example strings; the description supplies the slug/name equivalence and the ranking semantics.

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 and scope: the top of one category's Substack leaderboard, plus the exact fields returned (followers, paid band, move since the previous board). That is far more concrete than the bare name 'board'. It stops short of explicitly contrasting itself with siblings like list_categories or get_writer, so it earns a 4 rather than a 5.

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 real selection guidance for the 'board' parameter, stating that 'bestsellers' (ranked by paid subscribers) is the default and 'rising' means recent paid growth, so an agent knows which value fits which intent. It also covers the main failure path — a non-matching category returns the closest categories — which tells the agent how to recover. It does not name an alternative tool for pure category browsing, so no explicit 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.