Skip to main content
Glama
explorium-ai

Explorium AgentSource MCP Server

Official
by explorium-ai

autocomplete

Autocomplete values for business fields like country, job title, or company size by providing a query string to get valid filter options.

Instructions

Autocomplete values for various business fields based on a query string.
You MUST call this tool before using any of the following filters:
- country
- country_code
- region_country_code
- google_category
- naics_category
- linkedin_category
- company_tech_stack_tech
- company_tech_stack_categories
- job_title
- company_size
- company_revenue
- number_of_locations
- company_age
- job_department
- job_level
- city_region_country
- company_name

Use this tool to get a list of possible enum values for filters.
Call this tool simultaneously as many times as possible. Do not call it
sequentially.

Prefer to use linkedin_category over google_category.

Hints:
- When looking for 'saas' in categories, use 'software'
- Use 'country' to get the country code

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldYesThe field to autocomplete. Must be one of the supported filters such as 'job_title' or 'company_size'.
queryYesThe query to autocomplete
Behavior4/5

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

No annotations provided, but description gives strong behavioral hints (parallel calls, field dependencies). Could explicitly declare read-only nature, but it's implicitly clear for autocomplete. Good coverage.

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?

Well-structured with clear sections, lists, and hints. Front-loaded with purpose. Slightly long but every sentence adds value.

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?

No output schema and description does not mention return format (e.g., list of suggestions). Successful response structure and error handling are missing, leaving some ambiguity for an agent.

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% with enum and descriptions. Description adds value by listing all fields inline and providing hints (e.g., 'software' for 'saas'), but semantics are already well-covered by schema.

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?

Description states 'Autocomplete values for various business fields based on a query string' with a clear list of specific fields. It distinguishes itself from sibling enrich/fetch tools by being a utility for filter selection.

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

Usage Guidelines5/5

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

Explicitly states 'You MUST call this tool before using any of the following filters', lists 17 filters, advises calling simultaneously, and provides preference for linkedin_category over google_category.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/explorium-ai/mcp-explorium'

If you have feedback or need assistance with the MCP directory API, please join our Discord server