Skip to main content
Glama

Company Framework

List the Fathomed bots

list_fathomed_bots
Read-only

Lists the Fathomed bots, free AI assistants for the trades (estimators, follow-up writers, collectors and more), with each one's slug, trade, release date, Grok link and plain-text instructions URL. Takes an optional filter word, such as a trade.

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

Input Schema

NameRequiredDescriptionDefault
filterNoOptional word to filter on, such as fence, roofing or collections.

Output Schema

NameRequiredDescriptionDefault
botsYes
totalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/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 that this is a fixed curated catalog of AI assistants and details the exposed fields, but says nothing about ordering, pagination, or how partial matches on the filter behave.

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 compact sentences with the purpose and returned fields front-loaded, followed by the parameter note. There is minor redundancy between the field list here and the output schema, but nothing that wastes the reader's time.

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?

With one optional parameter, full schema coverage, a live output schema, and read-only annotations, the description covers what an agent needs to select and invoke it. Only the return ordering and filter-matching semantics are left implicit, which is minor at this complexity.

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 description coverage is 100% and the single `filter` parameter is already documented with examples (fence, roofing, collections). The description repeats the same examples without adding syntax, matching behavior, or case-sensitivity details, so it adds no meaning beyond the schema.

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?

"Lists the Fathomed bots" names a specific verb and resource, and the enumeration of returned fields (slug, trade, release date, Grok link, instructions URL) makes it unambiguous that this is a catalog listing rather than a single-record fetch like get_fathomed_bot. It stops short of naming the singular sibling explicitly, so differentiation is inferential rather than stated.

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

Usage Guidelines3/5

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

The description implies when the filter is useful ("such as a trade"), but gives no explicit guidance on when to call this versus get_fathomed_bot, nor any when-not condition. Usage is inferable from the plural scope but not spelled out.

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.

Resources