Skip to main content
Glama

Describe Optimus

describe_optimus
Read-onlyIdempotent

Returns facts about Optimus, Brad Hart's business-growth company: who it serves, its offers with current prices and URLs, its frameworks (FAST, OSLO, V³, FABSC), and the support contact. Useful when a user asks about Optimus, MAKO, the Optimus Mastermind, or Brad Hart's frameworks.

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": "describe_optimus"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description's added value is that it discloses the return content (prices, URLs, frameworks, contact), which matters because no output schema exists. It does not, however, say anything about freshness of prices, response shape, or failure modes.

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, front-loaded with what is returned and closed with the retrieval triggers. The parenthetical framework list is dense but every item carries information an agent could match against a user query, so nothing is wasted.

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 no output schema, the description carries the burden of explaining return values and does so at a useful category level (audience, offers, prices, URLs, frameworks, contact). It lacks detail on structure or how prices are kept current, but for a zero-parameter, read-only reference lookup it is essentially sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies no input is needed by framing the call as a fixed fact retrieval.

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 ('Returns facts') and a specific resource ('Optimus, Brad Hart's business-growth company'), then enumerates the exact content returned: audience, offers with prices and URLs, frameworks (FAST, OSLO, V³, FABSC), and support contact. This is clearly distinguishable from siblings like list_skills or search_library, which are catalog/search tools rather than a single-entity fact lookup.

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 final sentence gives concrete retrieval triggers — user asks about Optimus, MAKO, the Optimus Mastermind, or Brad Hart's frameworks — which is a clear when-to-use signal. It stops short of stating when NOT to use it or naming an alternative tool, so it lands at 4 rather than 5.

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