Skip to main content
Glama

Swift Agent Network: Local Agents, Movers & Contractors

Get one member

get_member
Read-onlyIdempotent

One network member by slug (the slug comes from search_members or from the member page URL, swiftagentnetwork.com/members//). Carries book when they take bookings and have an open time in the next 7 days.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe member's slug, e.g. "jane-doe".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description does add a payload hint ('Carries book when they take bookings and have an open time in the next 7 days'), which tells the agent the record encodes booking availability — genuinely beyond the annotations, but the phrasing is ambiguous enough that the meaning is not fully reliable.

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?

Two sentences, front-loaded with the core action and the key parameter source. The trailing sentence about bookings is compressed to the point of near-unintelligibility, which costs some clarity but not length.

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 one-parameter read tool with full schema coverage, strong annotations, and no output schema, the description supplies the lookup key source and a hint at the returned availability data. Only the vague second sentence leaves an agent slightly unsure what the response contains.

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 slug property already documents format with an example. The description's contribution is the provenance of the slug (search_members or member page URL), which is useful but supplemental; baseline 3 applies when the schema carries the parameter detail.

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?

States a specific retrieval: 'One network member by slug', naming both the resource and the lookup key. It implicitly separates itself from search_members by framing this as the single-record fetch, though it never explicitly says 'use search_members to find candidates first' as a contrast.

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?

Gives concrete context for when this applies: after search_members or from a member page URL pattern (swiftagentnetwork.com/members/<slug>/). No explicit when-not-to-use or stated alternatives beyond the slug source, so it falls short of a full 5.

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.