Skip to main content
Glama

Check business fit

fit_check
Read-onlyIdempotent

Check whether a founder's business is a fit for Optimus offerings and get the right next step. Deterministic, no data stored. Pass what the founder told you: revenue, team size, their role, which of Offers / Sales / Leads / Operations is tightest, and what they want.

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

Input Schema

NameRequiredDescriptionDefault
roleNoThe person's role, e.g. founder, CEO, marketing manager
wantsNoWhat they are trying to get done, in their words
team_sizeNoPeople on the team, if known
constraintNoWhich part of the business is tightest: offers, sales, leads, or operations
revenue_usdNoAnnual revenue in USD, if known

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 (readOnly, idempotent, non-destructive, closed-world), yet the description still adds genuinely new behavioral facts: the check is deterministic and 'no data stored', which tells an agent the call is repeatable and privacy-safe. It stops short of describing what the recommendation response looks like.

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 tight sentences with the purpose front-loaded first and the invocation guidance second. Every clause carries information; nothing is redundant with 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 no output schema, the description must hint at returns, and 'get the right next step' does so at a high level. All five parameters are optional and self-reported, which the description implicitly covers, but the shape of the fit verdict itself is left unexplained.

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. The description adds mild value by framing the inputs as founder-reported ('pass what the founder told you') and reiterating the four constraint buckets, but it introduces no format, fallback, or unknown-value semantics beyond the schema.

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?

Specific verb and resource: 'Check whether a founder's business is a fit for Optimus offerings and get the right next step.' That is clearly distinct from sibling tools like describe_optimus or list_packs, though the description never explicitly names an alternative to route against.

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?

The second sentence explains how to invoke it ('Pass what the founder told you...') but not when to prefer it over siblings or when it is inappropriate. Usage is implied by the concept of 'fit', not stated as a condition.

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