Skip to main content
Glama

Resume Booster Job Board

Board statistics

board_stats
Read-onlyIdempotent

Board statistics from a five-minute cache: servable and tracked posting totals, the count of company job boards with open roles (boards, not employers), the category slugs search_jobs takes, and what this connector does not hand on. Answers with no key and is never counted.

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": "board_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteNo
cachedAtNo
categoriesYes
refreshedAtNo
excludedSourcesNo
trackedPostingsNo
servablePostingsYes
openCompanyBoardsYes
freshnessWindowDaysYes
openCompanyBoardsBasisYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / properties / cachedAt
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / categories / description
      Removed value: -"The category slugs search_jobs accepts."
    • addedOutput schema / properties / excludedSources
      Added value: +{
      +  "type": "object"
      +}
    • removedOutput schema / properties / openCompanyBoards / description
      Removed value: -"Company job boards with at least one servable posting. BOARDS, not employers — read openCompanyBoardsBasis."
    • removedOutput schema / properties / refreshedAt / description
      Removed value: -"When the cache these figures come from was last written."
    • removedOutput schema / properties / servablePostings / description
      Removed value: -"Postings the board serves right now: not withdrawn, dated within the freshness window. Null when the pass did not compute it."
    • removedOutput schema / properties / trackedPostings / description
      Removed value: -"Every posting the board holds, including ones outside the serving rules."
    • removedOutput schema / properties / withKey
      Removed value: -{
      -  "description": "Present on an unkeyed call: where a free key comes from and what it adds.",
      -  "properties": {
      -    "adds": {
      -      "description": "What a free key opens beyond the unkeyed tools.",
      -      "type": "string"
      -    },
      -    "dailyCalls": {
      -      "description": "Calls a day on a free key.",
      -      "type": "integer"
      -    },
      -    "mintUrl": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "mintUrl",
      -    "dailyCalls",
      -    "adds"
      -  ],
      -  "type": "object"
      -}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior. The description adds useful behavioral context beyond that: results come from a five-minute cache, no key is required, and calls are never counted against quotas.

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 description is a single dense sentence that front-loads the cache fact but becomes cluttered with parentheticals and an vague phrase about 'what this connector does not hand on.' It could be cleaner and more skimmable.

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 return-value structure need not be explained. The description covers the key operational context—cache freshness, no-key access, and quota behavior—and is adequate for a zero-parameter statistics tool.

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 zero parameters, so the schema baseline is 4. The description appropriately does not invent parameter semantics, though mentioning category slugs relates to search_jobs rather than this tool's own input.

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 specifies the resource (board statistics) and enumerates the concrete metrics returned: servable and tracked posting totals, company job board counts with open roles, and category slugs. It also clarifies the 'boards, not employers' distinction, which helps separate it from sibling employer tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied as a statistics/diagnostic endpoint, and the description notes it answers with no key and is never counted. However, it does not explicitly say when to call this instead of siblings like search_jobs, get_jobs, or employer_growth.

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.