Skip to main content
Glama

Company Framework

Request a Fathomed bot

request_a_bot

Sends a request for a new Fathomed bot to Company Framework: what the bot should do and for which trade, with an optional email for word when it ships. Requests are read weekly; one requested bot can ship each week.

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": {
      "idea": "<idea>"
    },
    "name": "request_a_bot"
  }
}

Input Schema

NameRequiredDescriptionDefault
ideaYesWhat the bot should do, in a sentence or two.
emailNoOptional. Where to say it shipped.
tradeNoThe trade or kind of business.

Output Schema

NameRequiredDescriptionDefault
messageYes
receivedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: the weekly review cadence and the one-bot-per-week throughput ceiling, which is exactly the kind of expectation-setting an agent needs. It stops short of saying whether a submission returns a tracking reference or whether duplicate ideas are deduplicated.

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?

Two sentences, both load-bearing: the first defines the submission and its payload, the second front-loads the processing cadence and throughput limit. No filler and no repetition of the title.

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 an output schema present and full parameter coverage, the description needn't explain return values, and annotations carry the mutation safety profile. What is supplied — payload, cadence, throughput — is sufficient to call the tool correctly, with only the deduplication/tracking question left open.

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%, so the baseline is 3 regardless. The description restates the same three fields (idea, trade, optional email) at roughly the same level of detail as the schema, adding no format, length, or validation guidance beyond it.

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?

States a specific verb and resource — sending a request for a new Fathomed bot to Company Framework — plus the content the request carries (behavior, trade, optional contact email). This is plainly distinguishable from the retrieval siblings get_fathomed_bot and list_fathomed_bots without opening any schema.

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

Usage Guidelines4/5

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

The description supplies real operational context for choosing this tool: requests are reviewed weekly and at most one requested bot can ship per week, which tells an agent this is an asynchronous, best-effort submission rather than an instant provisioning call. It does not, however, state any exclusions or point to an alternative path for a user who wants an existing bot.

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