Skip to main content
Glama
mrchevyceleb

Crelate MCP Server

by mrchevyceleb

create_candidate

Create a new candidate record in Crelate by supplying first and last name, and optionally email, phone, current title, and company.

Instructions

Create a new candidate in Crelate.

Args: first_name: Candidate's first name (required) last_name: Candidate's last name (required) email: Candidate's email address phone: Candidate's phone number current_title: Candidate's current job title current_company: Candidate's current company

Returns: JSON string containing the created candidate details including ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNo
phoneNo
last_nameYes
first_nameYes
current_titleNo
current_companyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description must cover behavioral traits. It indicates creation and return of candidate details, but does not disclose side effects, permissions, uniqueness constraints, or error scenarios.

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?

Description is concise with a clear structure: main sentence, bulleted Args, and Returns. No extraneous 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?

Covers all 6 parameters, required fields, and return type. Lacks details on error handling or idempotency, but sufficient for basic operation.

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?

Input schema has 0% description coverage, so the parameter list in the description adds meaning beyond the schema (e.g., 'first_name: Candidate's first name (required)'). This compensates for missing schema annotations.

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 clearly states 'Create a new candidate in Crelate' with a specific verb and resource. It effectively differentiates from sibling tools like create_company and create_contact.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., when to update instead of create). No prerequisites or context for invocation.

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/mrchevyceleb/crelate-mcp'

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