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

Smitline: AI Phone Calls & Meetings

How to use Smitline

how_to_smitline
Read-only

Answer questions about Smitline: what it is, how calls work, pricing, account limits, refusals, and rules.

Instructions

Information about Smitline itself, to answer the user: what it is, who makes it and first things to try, how calls work, what calls cost, the user's account (plan, call limits, balance), what a refusal means, and Smitline's rules. Useful when the user has just connected Smitline or asks whether it is connected, when the user asks about Smitline, its prices or their account, or when a call was refused. Returns a few short paragraphs and links.

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

Input Schema

NameRequiredDescriptionDefault
topicNooverview (the default): what Smitline is, who makes it, and first things to try. using: how calls work. following: the two ways to run a call, letting it run or following it live. pricing: what calls cost. account: the user's plan, call limits and balance now. troubleshooting: what refusals and common problems mean. rules: what Smitline does and does not do.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.12

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by declaring the return shape: 'a few short paragraphs and links,' which tells the agent to expect prose rather than structured data. It omits any note on freshness or whether account data is live, which is the only material gap.

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?

The purpose is front-loaded in the opening clause, and the topic list and trigger list follow in a logical order. The single long sentence is dense but nearly every clause maps to a distinct capability or trigger, so little could be cut without losing routing information.

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?

With one optional parameter, no output schema, and simple annotations, the description supplies everything an agent needs: what the tool answers, when to call it, and roughly what comes back. The default topic is documented in the schema, so its absence from the prose is not a defect.

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% and the enum values each carry their own descriptions, so the schema does the heavy lifting. The description reinforces the mapping by tying user questions (prices, account, refusals) to topics, but adds no format or precedence guidance beyond that. Baseline 3 is appropriate.

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?

The description states a specific resource (information about Smitline itself) and enumerates the exact content it covers: what it is, who makes it, first things to try, how calls work, cost, account state, refusal meaning, and rules. This is unmistakably distinct from the call-management siblings, which operate on calls, contacts, and voices rather than answering questions about the product.

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?

Trigger conditions are stated concretely: when the user has just connected Smitline or asks whether it is connected, asks about Smitline/prices/their account, or when a call was refused. That covers the realistic entry points well. It stops short of explicit exclusions or naming an alternative for overlapping questions, so it is clear context rather than a full routing rule.

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