Skip to main content
Glama
lapras-inc

lapras-mcp-server

Official
by lapras-inc

create_experience

Add a new work experience entry to your LAPRAS CV with details like organization, positions, dates, and client work status.

Instructions

Create a new work experience on LAPRAS(https://lapras.com). You can check the result at https://lapras.com/cv

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_yearYesEnd year (0 if ongoing)
end_monthYesEnd month (0 if ongoing)
positionsYesList of position type IDs - multiple selections are allowed. Please set relevant position types.
start_yearYesStart year
descriptionNoDetailed description of the experience (Markdown format)
start_monthYesStart month
position_nameNoPosition title
is_client_workYesWhether this is client work (Set to true when the affiliated company and the project client are different, such as in contract development companies)
organization_nameYesName of the organization
client_company_nameNoClient company name (required only when is_client_work is true)
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Create' without mentioning mutation, authentication requirements, or side effects. The result URL is helpful but insufficient.

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?

Two concise sentences: one for the action and one for the result URL. No unnecessary words, though it could be slightly more structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is minimal. It lacks context about authentication, required permissions, or what constitutes a successful creation. The sibling tools are not referenced.

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?

All 10 parameters have descriptions in the schema (100% coverage). The description adds no additional meaning beyond the schema, meeting the baseline for high coverage.

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 uses a specific verb 'Create' and clearly identifies the resource 'work experience' on LAPRAS. It distinguishes from sibling tools like update_experience and delete_experience.

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. It does not mention prerequisites or scenarios where other tools (e.g., update_experience) would be more appropriate.

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/lapras-inc/lapras-mcp-server'

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