Fathom-Simple-MCP

by druellan

Overview Schema Source Related Servers Discussions Admin

Python

list_team_members

Read-only

Retrieve paginated team members, optionally filtered by team name, to browse or paginate through member lists.

Instructions

Retrieve paginated team members with optional team filtering.

Examples: list_team_members_tool() # Get all team members across all teams list_team_members_tool(team="Engineering") # Filter members by team name list_team_members_tool(cursor="def456") # Paginate through member list

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_team_members"
  }
}

Input Schema

Name	Required	Description	Default
`team`	No
`cursor`	No
`per_page`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.2.0Jul 28, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / cursor / anyOf

Added value: +[
+  {
+    "description": "Pagination cursor",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / cursor / description
```
Removed value: -"Pagination cursor"
```
removedInput schema / properties / cursor / type
```
Removed value: -"string"
```

addedInput schema / properties / per_page / anyOf

Added value: +[
+  {
+    "description": "Number of results per page (default: 50)",
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / per_page / description

Removed value: -"Number of results per page (default: 50)"

removedInput schema / properties / per_page / type
```
Removed value: -"integer"
```

addedInput schema / properties / team / anyOf

Added value: +[
+  {
+    "description": "Filter by team name",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / team / description
```
Removed value: -"Filter by team name"
```
removedInput schema / properties / team / type
```
Removed value: -"string"
```

Addedv1.0.0Jan 3, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Description aligns with readOnlyHint annotation, stating 'Retrieve'. Adds context about pagination and filtering but does not disclose other behaviors like rate limits, order, or error handling. Adequate given simple read operation.

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?

Description is concise with a single sentence and relevant examples, front-loading purpose. No unnecessary words.

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 list tool with output schema, the description covers pagination and filtering. Could mention default per_page value, but overall sufficient. Output schema fills gaps.

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?

Despite 0% schema description coverage per context signals, the description provides examples that demonstrate parameter usage. The examples help clarify team and cursor parameters, though per_page default is not mentioned. Partial compensation.

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 name and description clearly indicate the tool retrieves paginated team members with optional team filtering, distinguishing it from sibling tools like list_teams which list teams, not members.

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?

Examples show when to use the tool: default all members, filter by team, paginate. Usage is implied, but no explicit guidance on when not to use or alternatives. Clear enough for most cases.

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

Deploy Server