Skip to main content
Glama

Remote Nomad Jobs

Get company profile

get_company
Read-onlyIdempotent

A company's profile on Remote Nomad Jobs: what it does, how many work-from-anywhere jobs it has open, its main job categories, and its newest open 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"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCompany name (e.g. 'GitLab') or its remotenomadjobs.com company URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds what the response contains (job counts, categories, newest jobs), which matters because there is no output schema, but it says nothing about behavior when the company name is ambiguous or missing, nor how many 'newest open jobs' are returned.

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 tight sentence with zero filler, and the payoff (what the profile contains) is front-loaded. It could be improved by leading with a verb such as 'Get...' to make the action unambiguous, but nothing is wasted.

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?

For a one-parameter read-only lookup with rich annotations but no output schema, the description's return-content inventory carries the important missing information. What remains uncovered—not-found/ambiguous-name behavior and result limits on newest jobs—is modest but non-trivial.

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 description coverage is 100% and the single parameter already documents that it accepts a company name (e.g. 'GitLab') or a remotenomadjobs.com company URL. The description adds no meaning beyond that—no note on ambiguous name resolution or URL format expectations—so the baseline 3 applies.

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 (a company's profile on Remote Nomad Jobs) and enumerates the concrete contents returned: what it does, work-from-anywhere job count, main job categories, and newest open jobs. It is clearly a single-company detail fetch, but it is phrased as a noun fragment with no verb and never distinguishes itself from the sibling search_companies (list/find) versus this per-company lookup.

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 only implied: the enumerated contents suggest 'use this when you want an overview of one specific company, including its open jobs.' There is no explicit when-to-use, no when-not-to-use, and no reference to search_companies as the alternative when the company is not yet identified.

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