Skip to main content
Glama
Sign In

openradar

by io.github.MikhailSagalaev
OverviewDiscussionsAdmin

estimate_compensation

Estimate market compensation (median, 25th and 75th percentiles, sample count, and typical skills) for a role, tech stack, or seniority level across recent leads.

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": {
      "type": "<type>"
    },
    "name": "estimate_compensation"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesjob = employment (monthly pay), gig = freelance order (project budget)
gradeNoSeniority level
titleNoJob title or role description, e.g. "Senior Python Developer"
skillsNoTech stack, e.g. ["Python", "FastAPI"]
currencyNoPreferred currency for results (default RUB)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that results are derived from 'recent leads' and that a sample count is returned, but it says nothing about behavior when data is sparse, whether estimates are cached, currency-conversion handling, or that the operation is a safe read-only computation.

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?

A single, front-loaded sentence with the verb first and the returned statistics enumerated; there is no filler. It is dense but every clause contributes information an agent needs.

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?

With no output schema, the description usefully lists what the tool returns, and all five parameters are documented in the schema. What is missing is the behavioral envelope (insufficient-sample behavior, read-only nature), which matters more given the absence of annotations.

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 enums are documented for type, grade, and currency, so the schema does the heavy lifting. The description only loosely maps its phrasing to title/skills/grade and adds no format or default details beyond the schema (e.g. RUB default is already in 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 names a specific verb (estimate) and resource (market compensation) and enumerates the concrete outputs: median, 25th/75th percentiles, sample count, and typical skills. It does not explicitly differentiate itself from siblings such as get_market_analytics, so it stops 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 Guidelines3/5

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

Usage is only implied by the phrase 'for a role, tech stack, or seniority level across recent leads', which suggests the inputs but gives no when-to-use/when-not guidance and never names the alternative analytics tool. An agent must infer which sibling to pick.

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

All openradar 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