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.7/5.0
Behavior3/5

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

The annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description only needed to add context, and it does add the domain framing and content summary. However, it leaves a real behavioral gap: "filter word" never says which fields the word is matched against (name, trade, slug?) or whether it is substring or exact, which matters for a listing call.

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?

The first sentence front-loads the verb, the resource, and the domain definition, and the second covers the parameter in one clause with no filler. Minor deduction because the return-field enumeration partly restates what the existing output schema already declares.

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?

This is a simple, zero-required-parameter list tool with full annotation coverage and an output schema, so the description does not have to explain return values. What is missing is small but real: whether results are paginated or sorted, and how the filter word is applied.

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 schema's own filter description already supplies examples (fence, roofing, collections), so the baseline applies. The description's "such as a trade" marginally narrows intent but does not resolve the matching semantics the schema also leaves open, so it adds little beyond structured data.

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 gives a specific verb and resource ("Lists the Fathomed bots") and immediately defines what those bots are ("free AI assistants for the trades"), so an agent knows the domain and the payload. It also enumerates what each entry carries (slug, trade, release date, Grok link, instructions URL), which clearly separates this bulk operation from the singular sibling get_fathomed_bot.

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?

Usage is only implied: "Takes an optional filter word, such as a trade" signals the tool works with or without narrowing, but the description never says when to reach for this list versus get_fathomed_bot or the search siblings. There is no explicit exclusion or routing condition for an agent to apply.

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