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

Smitline: AI Phone Calls & Meetings

Read your profile

get_profile
Read-only

Reads the user's profile—identity, contacts, communication style, boundaries, default call/meeting voices, and wallet balance/spend—so agents can personalize interactions and respect limits.

Instructions

Read the user's profile, which every call gets as background: who they are, the people they know (name, relationship, phone, notes), how they like to come across, and standing boundaries. voices has the default voices for phone calls and for meetings. On a hosted service such as Smitline Cloud it also has the account's wallet: what is left to spend, and this month's spend.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description does add genuine value beyond them: it discloses that the profile is automatically attached as background to every call, and that the wallet section appears conditionally only on hosted services such as Smitline Cloud — a non-obvious environment-dependent behavior.

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 purpose in the first clause, then the contents. Three sentences, all earning their place, though the wallet sentence is slightly longer than needed for what is essentially one conditional field group.

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

Completeness5/5

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

There is no output schema, so the description must carry the return-value burden, and it does — naming each section of the profile plus the two environment-conditional pieces (default voices, Cloud wallet). For a zero-parameter read tool this is complete enough to call blind.

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?

Zero parameters, so the baseline of 4 applies. The description usefully explains the shape of the returned record (contacts, voices, wallet) even though there is nothing to parameterize.

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?

States a specific verb ("Read") and resource ("the user's profile") and then enumerates the concrete content — identity, contacts with relationship/phone/notes, tone preferences, and standing boundaries. An agent knows exactly what it gets back without opening anything else, and the read-only nature is unambiguous against update_profile.

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?

Usage is only implied by the phrase "which every call gets as background," which hints this is context-loading rather than a filtered query. It never names update_profile or list_contacts as the alternative for mutation or per-contact lookup, and gives no explicit when-to-call trigger.

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