Skip to main content
Glama

OpenNash Jobs

Resolve company coverage

get_company_coverage
Read-onlyIdempotent

Resolve an employer name, brand or company_uri and show its coverage: observation date, freshness, coverage gaps and observed job count. Partial names list candidates (10 per page; ask the user when ambiguous). Only Forbes Global 2000 companies are covered; an uncovered company is not one with zero jobs.

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": {
      "company": "<company>"
    },
    "name": "get_company_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoCandidates per page.
offsetNoResults to skip, for paging.
companyYesEmployer name, brand or company_uri.

Output Schema

NameRequiredDescriptionDefault
limitYes
totalYes
offsetYes
matchesYes
has_moreYes
warningsYes
evidence_dateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / company / description
      Added value: +"Employer name, brand or company_uri."
    • addedInput schema / properties / company / maxLength
      Added value: +160
    • addedInput schema / properties / company / minLength
      Added value: +1
    • removedInput schema / properties / company / title
      Removed value: -"Company"
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 10,
      +  "description": "Candidates per page.",
      +  "maximum": 50,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Results to skip, for paging.",
      +  "maximum": 10000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • removedInput schema / title
      Removed value: -"get_company_coverageArguments"
    • addedOutput schema / $defs
      Added value: +{
      +  "CompanyCoverage": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "company_name": {
      +        "default": null,
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "company_uri": {
      +        "type": "string"
      +      },
      +      "coverage_status": {
      +        "default": null,
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "freshness_status": {
      +        "default": null,
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "last_verified_at": {
      +        "default": null,
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "observed_jobs": {
      +        "default": null,
      +        "type": [
      +          "integer",
      +          "null"
      +        ]
      +      },
      +      "url": {
      +        "default": null,
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "required": [
      +      "company_uri"
      +    ],
      +    "type": "object"
      +  }
      +}
    • addedOutput schema / properties
      Added value: +{
      +  "evidence_date": {
      +    "default": null,
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "has_more": {
      +    "type": "boolean"
      +  },
      +  "limit": {
      +    "type": "integer"
      +  },
      +  "matches": {
      +    "items": {
      +      "$ref": "#/$defs/CompanyCoverage"
      +    },
      +    "type": "array"
      +  },
      +  "offset": {
      +    "type": "integer"
      +  },
      +  "total": {
      +    "type": "integer"
      +  },
      +  "warnings": {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  }
      +}
    • addedOutput schema / required
      Added value: +[
      +  "matches",
      +  "total",
      +  "has_more",
      +  "limit",
      +  "offset",
      +  "warnings"
      +]
    • removedOutput schema / title
      Removed value: -"get_company_coverageDictOutput"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior; the description adds useful domain behavior beyond that: only Forbes Global 2000 coverage and the rule that an uncovered company is not one with zero jobs. It also explains ambiguity handling, though it does not discuss auth or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three front-loaded sentences cover purpose, ambiguity/paging, and coverage boundary with no wasted wording. It does not redundantly restate annotations or the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema and rich annotations, the description supplies the remaining critical context: coverage scope, ambiguity handling, paging hint, and output dimensions. Nothing essential for correct invocation appears to be missing.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema by explaining that partial company names produce candidates and that the user should be asked when ambiguous.

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 ('Resolve') and resource ('employer name, brand or company_uri') and enumerates the coverage outputs, making the tool's function clear. The coverage focus distinguishes it from trend/search-style siblings even without naming them.

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?

Provides clear when-to-use cues for partial names (list candidates, ask the user when ambiguous) and an important exclusion (only Forbes Global 2000 companies are covered). It does not explicitly route to a sibling such as get_company_trends, so it stops short of full alternative 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