Skip to main content
Glama
Sign In
Ceki

Ceki

by Ceki-me
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search-specialists

Find specialists by skills, hourly rate, availability, and languages. Get profiles with rates and time slots.

Instructions

Search available specialists by skills, hourly rate range, availability, and languages. Returns profiles with rates and time slots.

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": "search-specialists"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination
skillsNoSkills to search for (e.g. ['React', 'TypeScript'])
max_rateNoMaximum hourly rate in USD
min_rateNoMinimum hourly rate in USD
availableNoOnly show currently available specialists
languagesNoLanguages the specialist should speak

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

A3.8/5.0
Behavior2/5

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

With no annotations, the description must disclose behaviors. It mentions returning profiles with rates and time slots, but omits details like authentication needs, rate limits, side effects, or how 'available' is interpreted. The behavioral info is incomplete.

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?

Two concise sentences with no wasted words. Front-loaded with the main verb and resource, then return info. Every part earns its place.

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?

Given 6 parameters and no output schema, the description covers the search purpose and return structure. It lacks detail on pagination (page parameter) but is otherwise adequate for a search tool with schema-covered params.

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 parameters are documented. The description adds meaning by grouping filters and stating returns (rates, time slots), which is not in schema. It clarifies the 'available' boolean and 'time slots' output, adding value beyond 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?

The description clearly states the tool's purpose: 'Search available specialists by skills, hourly rate range, availability, and languages.' It specifies the verb (search), the resource (specialists), and the filters, distinguishing it from sibling tools like get-pricing or register-agent.

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?

The description provides context for when to use the tool (searching specialists), but does not mention when not to use it or suggest alternatives among siblings. No explicit usage guidance is given.

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

Deploy Server

Other Tools