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

Smitline: AI Phone Calls & Meetings

List your contacts

list_contacts
Read-only

Lists the people and businesses Smitline has called or been called by, including saved names, notes, call counts, latest call details, and whether calls carry over.

Instructions

List the people and businesses Smitline has called or been called by: each phone number with the name and notes the user saved, how many calls, the latest call, and whether earlier calls carry over automatically. Read-only and takes no arguments. Use list_calls with contact to see one contact's calls, and get_profile for the people the user described.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/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 'Read-only and takes no arguments' largely restates structured data. The genuinely additive part is the field-level description of what comes back, which matters because there is no output schema. However, scale, ordering, and pagination for the contact list are never addressed.

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 verb and resource, then the return contents, then the alternatives in a single clean sentence each. The middle clause listing six returned attributes is dense, and 'whether earlier calls carry over automatically' is vague enough to cost a point, but nothing is padding.

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

Completeness4/5

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

For a no-argument read tool with no output schema, the description carries the return-value burden well by naming the fields. What's missing is any sense of list size, ordering, or truncation behavior, which an agent might need when deciding whether to call it before drilling in with list_calls.

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?

With zero parameters the baseline is 4, and the description correctly signals 'takes no arguments', so the agent knows not to search for filters. The phrase 'takes no arguments' also implies no server-side filtering, which is useful framing even though the empty schema already conveys it.

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 (list) and resource (contacts), then defines the domain precisely: people and businesses the account 'has called or been called by'. It also enumerates the returned fields (phone number, saved name, notes, call count, latest call, carry-over), which distinguishes it clearly from call-level siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use list_calls with a contact to drill into one contact's calls, and get_profile for people the user described. That gives two named alternatives with the condition that selects each, so an agent doesn't have to guess between overlapping people-oriented tools.

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