Fathom-Simple-MCP

Overview Schema Source Related Servers Discussions Admin

list_teams

Read-only

Retrieve a paginated list of teams with their organizational structure. Use cursor and per_page parameters to navigate and control results.

Instructions

Retrieve paginated list of teams with organizational structure.

Examples: list_teams_tool() # Get first page of teams list_teams_tool(cursor="abc123") # Get next page using cursor

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

Input Schema

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

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 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"
```

Addedv1.0.0Jan 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true, so the description adds value by disclosing pagination behavior with cursor usage and provides examples, which is sufficient for a read-only list tool.

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?

The description is brief (two sentences plus examples), front-loaded with the core purpose, and every element is useful without redundancy.

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 simple list tool with an output schema, the description adequately covers pagination and structure, though it could mention fields returned. The output schema compensates, so overall it's sufficiently complete.

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?

The description does not elaborate on parameters beyond schema descriptions, which already cover cursor and per_page. The examples illustrate cursor usage but add minimal new semantic meaning.

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 uses a specific verb 'Retrieve' and resource 'teams', and the phrase 'paginated list with organizational structure' clearly distinguishes it from sibling tools like list_meetings or list_team_members.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives; no mention of prerequisites or when not to use it.

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

Deploy Server