Skip to main content
Glama

OpeningsFirst

Company jobs

company_jobs
Read-only

Every open job at one company (exact name as shown on 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": "company_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
companyYes
countryNoOptional country.
posted_within_daysNoDefault 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a real behavioral fact beyond that — results are limited to open jobs for a single company — but says nothing about pagination, ordering, or how the default 30-day recency window narrows the 'every open job' claim.

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?

One front-loaded sentence with the scope constraint leading and the parameter clarification trailing; no filler. It is arguably too terse for a 4-parameter filtered query, but nothing is wasted.

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

Completeness2/5

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

For a filtered list tool with no output schema, the definition omits pagination behavior and, more importantly, does not reconcile 'every open job' with the schema's 30-day default recency filter — an agent could easily misreport coverage. The description is not sufficient on its own to predict what comes back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% and the required 'company' parameter has no schema description, so the description's 'exact name as shown on jobs' genuinely adds semantics the schema lacks. However, 'page' and the interaction between 'posted_within_days' (default 30) and the promise of 'every open job' are left unexplained.

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?

States a specific resource and scope: all open jobs for exactly one company, which separates it from the broader search_jobs and the single-item get_job without naming them. The verb is implicit ('every open job at...') rather than an explicit 'list', which keeps it just short of 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 Guidelines2/5

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

There is no statement of when to use this instead of search_jobs, new_jobs, or my_jobs, and no exclusions or prerequisites. The parenthetical about the exact company name is parameter guidance, not usage 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