Skip to main content
Glama
Smitline: AI Phone Calls & Meetings

Smitline: AI Phone Calls & Meetings

Update your profile

update_profile
Idempotent

Save and revise user profile details, contacts by name, boundaries, and default phone or meeting voices so future calls and meetings use current preferences.

Instructions

Update the user's profile with what you know about them. Fields you pass replace the saved ones; people are added or updated by name; removePeople drops people. voices changes the user's default voice for phone calls, for meetings, or both, when the user wants another one. A call keeps its voice until it ends: when someone on a call asks for a different voice, it can only apply from the next call, so offer to change the default and do it once the user agrees. Never put passwords, keys, or payment details here.

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
aboutNoWho the user is: role, work, what they are building.
styleNoHow the user likes to come across on calls.
peopleNo
voicesNoDefault voices: phone for phone calls, meeting for meetings (by link or by phone). A name from list_voices, or "" to go back to the default. A brief's voice still wins for its call.
boundariesNo
removePeopleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.12
    • addedInput schema / properties / voices
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Default voices: phone for phone calls, meeting for meetings (by link or by phone). A name from list_voices, or \"\" to go back to the default. A brief's voice still wins for its call.",
      +  "properties": {
      +    "meeting": {
      +      "maxLength": 32,
      +      "type": "string"
      +    },
      +    "phone": {
      +      "maxLength": 32,
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare non-readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered elsewhere. The description still adds substantive behavior beyond that: replacement semantics ('Fields you pass replace the saved ones'), name-based upsert for people, removePeople as the delete path, and the rule that a voice change only applies from the next call. That call-continuity constraint is the kind of thing the agent would otherwise get wrong, though return behavior and effects of omission are unspecified.

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?

Front-loaded with the core action, then scoped replacement rules, then the voice edge case, then the safety exclusion. The voice sentences are long but each clause carries a distinct constraint, so little is padding. Slightly dense for a single paragraph, but no wasted sentence.

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 six params, a nested object array and no output schema, the description does a good job on upsert/remove and voice timing but leaves `boundaries` entirely undefined and never states what an update returns. An agent could call it correctly for most fields but would be guessing on boundaries.

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 50%, so the schema documents `about`, `style`, `people` and `voices` while leaving `boundaries` and `removePeople` bare. The description closes the removePeople gap and heavily enriches voices semantics (phone vs meeting, brief precedence is in the schema), but `boundaries` is never explained in either place, so the description only partly compensates for the coverage gap.

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 opens with a specific verb and resource ('Update the user's profile') and immediately scopes the content ('with what you know about them'), which cleanly separates it from the read-only get_profile sibling. It does not name any sibling explicitly, but the write/read contrast is unmistakable from the verb.

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?

It gives actionable when-to-use context, notably for `voices` ('when the user wants another one') and for the mid-call case ('offer to change the default and do it once the user agrees'). It also supplies a hard exclusion ('Never put passwords, keys, or payment details here'). What it lacks is any statement about when not to update at all, or which sibling to call for related tasks.

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