Kosmodrom

user_search

Read-only

Searches company employees by name, phone, email, department (role) and level; filters combine. With userID, returns one employee with the full profile, access and roles. Each employee comes with link (the name as a link) and mention (for a Kosmodrom chat message).

Input Schema

Name	Required	Description
`name`	No	Part of a first, last or middle name as written in the workspace; case-insensitive.
`role`	No	Department.
`email`	No	Exact email, case-insensitive, e.g. to match an assignee from GitLab or another external system.
`level`	No	Level or array of levels.
`limit`	No	Number of results (default 20, max 50).
`phone`	No	Phone number; formatting is ignored.
`userID`	No	One employee by ID, with the full profile; other filters are ignored.
`allowBlocked`	No	Include employees with blocked access; default false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

addedInput schema / properties / userID

Added value: +{
+  "description": "One employee by ID, with the full profile; other filters are ignored.",
+  "format": "uuid",
+  "type": "string"
+}

First observedOct 6, 2026

TDQS

A4.3/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, closed world), so the description earns credit for adding semantics the annotations don't: filters combine, userID overrides the other filters, and results carry link and mention fields for reuse in chat. It stops short of pagination/ordering behaviour, but it goes well beyond the annotation set.

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?

Three tight sentences with no filler, and the primary search capability is front-loaded ahead of the userID special case and the link/mention detail. The nested parentheticals (department (role), link (the name as a link)) make it slightly denser than it needs to be.

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 no output schema, the description correctly compensates by describing returns: single-result mode yields the full profile, access and roles. Combined with the documented filter-combination semantics it is largely sufficient, though result ordering and pagination behaviour for the 20/50 limit are left implicit.

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 the baseline is 3; the description still adds genuine meaning by stating that the filters combine (AND semantics), which the per-parameter descriptions do not express, and by clarifying the userID lookup mode. It adds little beyond that, so it sits just above baseline.

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+resource ("Searches company employees"), enumerates the exact filters, and separates the two operating modes: multi-result filtered search versus single-employee lookup via userID. No sibling tool searches people, so the agent can route to it without ambiguity.

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?

Clearly establishes when to use it (employee lookup by name/phone/email/department/level) and adds the key branch condition — pass userID to get one full profile, and other filters are then ignored. No exclusions or rate-limit guidance, but there is no competing user-search sibling to contrast against.

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

All Kosmodrom tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?