Skip to main content
Glama

Kariaa Agents

Update profile basics

update_profile

Use when the person gives the basics a task needs. Save the basics a task needs: legal first and last name, phone in E.164 (+1…), location as "City, Country", occupation (one to five titles, "student" is fine), language.

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": "update_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
languageNo
locationNo
occupationNo
phone_numberNo
legal_last_nameNo
legal_first_nameNo

Output Schema

NameRequiredDescriptionDefault
savedNoFields saved
missingNoStill missing
rejectedNoFields refused, with the reason
ready_to_applyNoBasics complete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish this is a non-read-only, non-destructive, non-open-world write. The description adds useful formatting constraints (E.164, 'City, Country', 1-5 titles) but never says whether the write merges or overwrites existing values, which matters given all 7 parameters are optional.

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 compact sentences with the trigger condition front-loaded, and no wasted preamble. The repeated phrase 'the basics a task needs' could be tightened, but the field-format list earns its space.

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

Completeness3/5

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

With an output schema present, return values need no explanation, and annotations cover the safety profile. Still, for a fully-optional mutation tool the description omits merge-vs-overwrite semantics and one of seven parameters, leaving real gaps for an agent to guess at.

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 description coverage is 0%, so the description must carry parameter meaning, and it largely does: it names six of the seven fields and supplies concrete accepted formats plus the permissive 'student' example for occupation. The only gap is email, which appears in the schema but is never mentioned in the description.

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

Purpose3/5

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

The verb is 'Save' and the resource is implied to be the person's profile basics, and the description enumerates the fields (legal name, phone, location, occupation, language). However, the framing 'the basics a task needs' is vague and never plainly states 'updates the current user's profile', so an agent must infer the resource from the tool name.

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?

'Use when the person gives the basics a task needs' is a real trigger condition, giving implied usage context. There is no exclusion guidance, no statement about what happens if a field is omitted, and no mention of related profile-reading tools such as whoami.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.