Skip to main content
Glama

Swift Agent Network: Local Agents, Movers & Contractors

How to contact a member

how_to_contact
Read-onlyIdempotent

The public ways to reach a network member: their page in the directory, their own website, and their phone if they show one there. This server does not send messages; give the person these links.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "how_to_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe member's slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value: it discloses that no message is sent, that the output is links, and that the phone number is conditional ('if they show one there'), which warns the agent a channel may be missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no wasted wording. The content is front-loaded with what the tool returns, followed by the key constraint about not sending messages.

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?

For a one-parameter read-only lookup with full annotation coverage and no output schema, the description covers what is returned, what is not possible, and how to use the result. Nothing needed to call it correctly is missing.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains 'slug'. The description adds no further semantics about slug format or lookup behavior, which is acceptable at the baseline for a fully documented single parameter.

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 names the specific resource (the public contact routes for a member: directory page, personal website, optional phone) rather than restating the title. It also explicitly rules out the most likely misreading by saying 'This server does not send messages', which separates it from any messaging interpretation an agent might bring.

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?

Usage is clear enough: use this when someone needs a way to reach a member, and pass the resulting links along ('give the person these links'). What's absent is explicit routing against siblings such as get_member or search_members, so the agent must infer that those serve profile lookup and discovery instead.

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.