Skip to main content
Glama

SourceGeek

Look up locations

employee_search_locations
Read-only

Resolve a city, region or country name to geo ids (geoId + canonical name) for the employee and company data searches, e.g. 'Amsterdam' → 102011674 'Amsterdam, North Holland, Netherlands'.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
keywordYesPlace name to look up, e.g. 'Amsterdam' or 'Netherlands'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open world). The description adds genuinely new behavioral context: the call disambiguates a bare place name into a canonical fully-qualified name, which signals how ambiguous inputs are resolved. It stops short of saying what happens when multiple places match or how ranking works.

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 that front-loads the purpose, then the return contract, then an inline example. No filler and nothing that could be cut without losing information.

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 only two parameters, full schema coverage, and annotations, the definition is nearly self-sufficient, and it compensates for the absent output schema by naming the returned fields. The remaining gap is match behavior for ambiguous names (single best match vs. list) and how limit interacts with disambiguation.

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 100% and both parameters are documented there, including limit bounds and the 'results beyond the provider's page are not fetched' caveat. The description only echoes the keyword intent with an example, so it adds little beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (resolve), a specific input class (city, region or country name), and the exact output shape (geoId + canonical name), plus a concrete worked example. It is clearly a resolver prerequisite rather than a record search, which separates it from the employee_search_* siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The phrase 'for the employee and company data searches' tells the agent this is a preparatory lookup whose geoIds feed other searches. It does not spell out an explicit when-not or name the consumer tools that require geoIds, so usage is clear but not fully 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.

Resources