Skip to main content
Glama

Company Framework

Open a Fathomed bot

get_fathomed_bot
Read-only

Returns the full written instructions of one Fathomed bot, given its slug.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe bot's slug, for example fence-estimator.

Output Schema

NameRequiredDescriptionDefault
botYes
instructions_textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds useful context: the payload is the bot's full written instructions, so the agent knows it is retrieving prompt-like content rather than metadata. It does not say what happens with an unknown slug, but that is a minor gap given the annotation coverage.

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?

A single well-formed sentence that front-loads the return value and ends with the input. Nothing is redundant and nothing important is buried.

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 an output schema and clear annotations, this is nearly complete: the agent knows what it gets and what it must supply. Only the error/not-found behavior for an invalid slug is left unstated.

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 even supplies a format example ("fence-estimator"). The description's "given its slug" adds no meaning beyond the schema, so the baseline 3 applies.

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?

"Returns the full written instructions of one Fathomed bot, given its slug" states a specific verb (returns) and resource (a single bot's instructions) plus the keying input. The word "one" implicitly separates it from list_fathomed_bots, but no sibling is named explicitly.

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: call it when you already have a slug and need that bot's instructions. There is no explicit when-to-use vs. when-not guidance, and no pointer to list_fathomed_bots for discovering a slug first.

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