Skip to main content
Glama

PickedJobs

Get company

get_company
Read-onlyIdempotent

Hiring summary for one company from its open jobs on PickedJobs: open roles by category, engineering specialty, seniority, work arrangement and region, top technologies, visa sponsorship count, listed US yearly salary range, website and careers-page check time. Accepts a company slug or name; a name that matches several companies returns the candidates. Does not use the job allowance.

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

Input Schema

NameRequiredDescriptionDefault
nameNoCompany name, used when the slug is unknown.
slugNoCompany slug, e.g. from a job’s companySlug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: ambiguous names do not error but return a candidate list, and the call does not draw on the job allowance (a quota/rate-limit trait not visible in structured fields).

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?

Front-loaded with the payload it returns, then the input contract, then the quota caveat — a sensible order with near-zero filler. The output enumeration sentence is dense but each item earns its place by telling the agent what the response contains in the absence of an output 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?

No output schema exists, so the description carries the return-value burden and does so by listing the fields of the summary. Inputs, ambiguity behavior and the allowance caveat are all covered, leaving nothing an agent needs in order to call it correctly.

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 baseline is 3, but the description adds meaning beyond the schema: slug is the preferred identifier with name as the fallback, and a multi-match name yields candidates rather than a single record. That tells the agent how to resolve the slug-vs-name choice in practice.

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 resource (one company's hiring summary from its open jobs) and enumerates exactly what the summary contains: category, specialty, seniority, work arrangement, region, technologies, visa count, salary range, website/careers check time. An agent can tell this is a per-company aggregate rather than a job listing or market-wide stat.

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?

It clarifies input handling (slug or name, ambiguous names return candidates) and notes it doesn't consume the job allowance, which hints at when it is cheap to call. But it never says when to prefer this over get_job or get_market_stats, so the choice between siblings is left to inference.

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