Skip to main content
Glama
Sign In

TeamedUp Intelligence — China & APAC Salary Data

by io.github.bp46
OverviewDiscussionsAdmin

get_company_jobs

Retrieve paginated historical job postings and salary bands for a specific company by its ID.

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_id": "<company_id>"
    },
    "name": "get_company_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor returned from a previous request (optional)
per_pageNoNumber of results per page (default: 50, max: 100)
company_idYesThe ID of the company to retrieve jobs for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does add one real behavioral detail – that results are 'paginated' and 'historical' (past postings, not live listings) – but it says nothing about auth requirements, rate limits, ordering, or what happens with an invalid company ID.

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?

A single sentence with the resource and scoping condition front-loaded and no redundant wording. Every clause carries information.

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

Completeness3/5

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

With no annotations and no output schema, the description should do more to explain the shape of a return or pagination behavior. It identifies the two data families (job postings, salary bands) adequately for a three-parameter read tool, but stops short of full behavioral coverage.

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%, so all three parameters, including cursor and per_page defaults, are already documented. The description only restates that lookup is 'by its ID', adding no syntax, format, or edge-case meaning beyond the schema.

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 states a specific verb (Retrieve), a specific resource (historical job postings and salary bands), and a scope (a specific company by ID). It does not explicitly distinguish itself from siblings like get_company_info or get_salary_trend, but the resource is narrow enough that an agent can tell what it returns.

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 when-to-use guidance, no exclusions, and no named alternative. The description implies the tool is for company-scoped job history, but it never says when to pick it over get_salary_trend or get_company_info, leaving routing entirely to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TeamedUp Intelligence — China & APAC Salary Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources