Skip to main content
Glama

Spanish Top Tech Companies

One company's salaries

company_salaries
Read-only

One company in Spain, any the site lists, down to one salary: overall, and by role, region or experience wherever it has salaries. Each figure says how many people it comes from, and few: true marks fewer than 5. Give a role, region or years to see the groups within it, combinations included. A name the site does not list gets close names to try. Companies listed apart under a name that starts like it (BBVA and BBVA Technology) come back in related_companies.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCompany name, e.g. Glovo.
roleNoRole slug or name, e.g. software-engineer, Data Scientist, product-manager. Omit for all roles.
yearsNoYears of experience, as a number such as 6 or a bucket such as 5-7. Omit for any experience.
regionNoSpanish region code or name, e.g. MD, Madrid, CT, Cataluña. Omit, or pass spain or remote, for all of Spain.
contextNoWhy are you calling this tool? Describe the goal in general terms, and refer to people by role ("a candidate") rather than by name. Leave out personal and identifying information.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description adds genuinely new behavior: every figure carries a sample-size count, 'few: true' flags groups of fewer than 5 people, unknown company names return close-name suggestions, and similarly prefixed companies (BBVA vs BBVA Technology) come back in related_companies. These are non-obvious response behaviors an agent would otherwise not anticipate.

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?

It is front-loaded with the core resource before the breakdown and edge-case behavior, and every sentence carries information. The phrasing is telegraphic and occasionally run-on ('and few: true marks fewer than 5', 'Companies listed apart under a name that starts like it'), which costs a little readability.

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?

No output schema exists, so the description must carry return-shape information, and it does: per-figure sample counts, the few flag threshold, related_companies, and close-name fallback. Combined with a fully documented schema, an agent has enough to call this correctly; only the exact response structure and free-parameter behavior remain unstated.

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 3 is the floor, but the description goes further by explaining the effect of each parameter: role/region/years produce grouped breakdowns, combinations are allowed, and an unlisted name triggers name suggestions. That adds semantic meaning about outcomes, not just accepted values.

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 resource and scope: one company's salary data in Spain, broken down overall or by role, region, or experience. It is clearly distinct from an aggregate tool like salary_stats, though it never names that sibling explicitly, so the agent must infer the split from context.

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 gives operational guidance on how to widen results ('Give a role, region or years to see the groups within it, combinations included') and what happens for unlisted names, but never states when to prefer this over salary_stats, top_companies, or find_jobs. Usage is implied rather than routed.

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.