Skip to main content
Glama

Spanish Top Tech Companies

Best-paying companies

top_companies
Read-only

Every company the site's companies table lists for a selection, by median base, highest first, down to one salary; companies with fewer than 3 salaries in the selection come after the rest. Each says how many people its figures come from, and few: true marks fewer than 5. Use search to look one company up within the selection.

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

Input Schema

NameRequiredDescriptionDefault
roleNoRole slug or name, e.g. software-engineer, Data Scientist, product-manager. Omit for all roles.
limitNo
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.
searchNoFilter companies by name.
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.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, openWorldHint false), yet the description still adds genuinely behavioral detail: results are ordered by median base descending, companies with fewer than 3 salaries are pushed to the end, each row reports its sample size, and few: true flags fewer than 5 salaries. That is exactly the kind of reliability/caveat context annotations cannot convey. It stops short of describing pagination or the full row shape, but the disclosed caveats are substantive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The ordering and threshold rules are front-loaded, which is good, but the first sentence is dense and awkwardly phrased ('lists for a selection ... down to one salary'), forcing the reader to parse twice. The 'Each says how many people its figures come from' clause could be tightened considerably.

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?

There is no output schema, so the description carries the burden of describing returned data, and it does cover ordering, sample-size fields, and the few flag. What remains unclear is the actual row shape (company name, median base value, other fields) and the meaning of 'down to one salary', which leaves a small but real gap for a no-output-schema tool.

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 coverage is 83%, so the schema already documents role, years, region, limit, and search, leaving the description little to add. The one real contribution is explaining that search filters within the ranked selection rather than replacing it; the 'few: true' explanation maps to output rather than input. 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 concrete verb-like behavior and resource: it ranks companies from the companies table by median base salary, highest first. It is specific about ordering and the small-sample tail, but the opening clause ('Every company the site's companies table lists for a selection') is convoluted and it never explicitly contrasts itself with siblings like company_salaries or salary_stats.

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 one concrete usage path — use the search parameter to look up a single company within the ranked selection — which implies this is a ranking/browse tool rather than a lookup tool. It does not say when to prefer it over company_salaries or salary_stats, nor any prerequisites or exclusions, so the guidance is only implied.

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.