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

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description does add one useful behavioral fact — that the returned payload is the *full written instructions* rather than a summary or metadata — but says nothing about size, truncation, or what happens if the slug is unknown.

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 sentence with zero filler, front-loaded with the return value and ending with the input requirement. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 a full annotation set and an output schema, the description covers the essentials. The gap is discoverability: an agent reading only this definition has no cue that list_fathomed_bots supplies the slug, which is the one piece of context a caller could actually need.

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 coverage is 100% and the schema already documents the single slug parameter with a concrete example ('fence-estimator'). The description's 'given its slug' adds no meaning beyond that, 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?

The description states a specific verb and resource — 'Returns the full written instructions of one Fathomed bot' — which tells an agent exactly what content comes back, not just that a bot is 'opened'. The word 'one' plus the slug requirement implicitly separates it from listing tools like list_fathomed_bots, but no sibling is named explicitly, so it stops short of a 5.

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: the caller must already hold a slug, which signals this is a retrieve-by-identifier operation. There is no statement of when to prefer this over request_a_bot or list_fathomed_bots, and no hint about how to obtain a slug in the first place.

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