Skip to main content
Glama

mcp-server

by me.ceki
OverviewDiscussionsAdmin

Search Specialists

search-specialists

[Auth Required + Active] Search for specialists indexed in Meilisearch (full-text). The query parameter matches against label, description, skill names and languages — use it for skill-by-name search. Paid action (api_search). Pass API key via X-Agent-Key or Authorization: Bearer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoAvailable until date (YYYY-MM-DD)
daysNoFilter by available days (ISO 1-7, Mon=1, Sun=7)
pageNoPage number
queryNoFree-text search (Meilisearch). Matches against label, description, skill names (e.g. "Python", "SEO"), language names. Use this for skill-by-name search instead of `skills` array.
startNoAvailable from date (YYYY-MM-DD)
skillsNoOptional filter by exact skill IDs. Use only when you already know IDs. For text/name-based skill search, prefer `query` parameter.
sortByNoSort field
perPageNoResults per page
currencyNoPrice currency filter
durationNoRequired duration in minutes
price_toNoMaximum price per hour
timezoneNoTimezone filter
hours_endNoFilter by availability end time (HH:MM)
descendingNoSort descending
price_fromNoMinimum price per hour
hours_startNoFilter by availability start time (HH:MM)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / days / description
      Previous value: -"Filter by available days (0=Sunday, 6=Saturday)"New value: +"Filter by available days (ISO 1-7, Mon=1, Sun=7)"
    • changedInput schema / properties / days / items / maximum
      Previous value: -6New value: +7
    • changedInput schema / properties / days / items / minimum
      Previous value: -0New value: +1
    • changedInput schema / properties / query / description
      Previous value: -"Free-text search query"New value: +"Free-text search (Meilisearch). Matches against label, description, skill names (e.g. \"Python\", \"SEO\"), language names. Use this for skill-by-name search instead of `skills` array."
    • changedInput schema / properties / skills / description
      Previous value: -"Filter by skill IDs"New value: +"Optional filter by exact skill IDs. Use only when you already know IDs. For text/name-based skill search, prefer `query` parameter."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses auth required, active status, and that the tool is a paid action (api_search). It also describes the search engine and matched fields. With no annotations, this provides reasonable transparency, though it could hint at output format.

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?

The description is two sentences, front-loading the core purpose and essential usage notes. Every word adds value; no redundancy or fluff.

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?

For a 16-parameter search tool with no output schema, the description covers the key aspects: purpose, auth, cost, and search behavior. It does not explain pagination or return format, but the schema covers pagination parameters. Overall adequate.

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%, so baseline is 3. The description reiterates the query parameter's matching behavior but adds little new meaning beyond the schema descriptions. Auth and paid info are not parameter-specific.

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?

The description clearly states the tool searches for specialists using full-text search via Meilisearch, specifying the fields matched (label, description, skill names, languages). This distinguishes it from sibling tools like search-browsers.

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 description includes auth and paid action requirements and advises using the query parameter for skill-by-name search instead of the skills array. However, it does not explicitly state when not to use this tool or compare it to alternatives.

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

All mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources