Skip to main content
Glama
lapras-inc

lapras-mcp-server

Official
by lapras-inc

update_experience

Update an existing work experience entry on your LAPRAS profile, including organization, positions, dates, and client work details.

Instructions

Update a 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
experience_idYesID of the experience to update
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?

Annotations are missing. The description only says 'Update a work experience' and 'check the result', but does not disclose side effects, idempotency, required permissions, or error conditions. The mutation nature is implied but not elaborated.

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. No redundancy, but the description is minimal. Could be restructured to include key details, but given the schema's completeness, it is acceptably concise.

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?

Despite 11 parameters, no output schema, and sibling tools, the description provides minimal context. It does not explain update behavior, how to interpret the result, or relationship to other tools. Incomplete for a complex mutation tool.

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 coverage is 100%, so the input schema already documents all parameters. The description adds no extra meaning beyond the schema, meeting the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Update' and resource 'work experience on LAPRAS'. It implicitly distinguishes from siblings like create_experience and delete_experience, but does not explicitly differentiate.

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 such as needing an existing experience_id, nor does it compare with create_experience or delete_experience.

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