Skip to main content
Glama

RZLT

Is a company a fit for RZLT?

check_fit
Read-onlyIdempotent

A quick, rule-based check of whether a company fits RZLT’s ideal client (technology companies, seed to Series C, €1M+ in revenue or funding). Fill in what you know; unknown fields can be left out. Returns a verdict (strong_fit, possible_fit, not_a_fit_yet), the reasons, services that match the goal, and the booking link.

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

Input Schema

NameRequiredDescriptionDefault
goalNoWhat they want to grow, in a sentence.
stageNoFunding stage.
marketNo
is_pre_revenueNo
is_tech_companyNoIs it a technology company (software, AI, hardware, deep tech, fintech…)?
is_local_businessNoA business serving one town or region in person (a restaurant, a clinic, a shop).
revenue_or_funding_eurNoAnnual revenue or total funding raised, whichever is higher, in euros.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 a closed-world scope, so the safety profile is covered. The description adds real value by disclosing the return payload (verdict enum values, reasons, matching services, booking link) and that it is rule-based rather than a model judgment. It stops short of explaining how missing fields affect the verdict.

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?

Three sentences: what it checks and against which criteria, how to supply inputs, and what comes back. The order is exactly the order an agent needs it, and no sentence is redundant.

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 adequately by naming the three verdicts and the accompanying reasons, services and booking link. The one gap is how partial inputs trade off against verdict confidence, which matters given all seven parameters are optional.

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 71%, so the schema already documents most fields; the description's contribution is the qualification thresholds behind is_tech_company, stage and revenue_or_funding_eur (seed to Series C, €1M+). It says nothing about goal, market, is_pre_revenue or is_local_business, leaving a few parameters to the schema alone.

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 (a rule-based fit check for RZLT's ideal client) and even spells out the qualifying criteria: technology companies, seed to Series C, €1M+ revenue or funding. It is easy to distinguish from a search or booking tool on intent alone, though it never names a sibling to contrast with.

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?

There is genuine guidance on input handling ('Fill in what you know; unknown fields can be left out'), which tells the agent how to call it with partial data. But there is no explicit statement of when to reach for this versus rzlt_overview, search_rzlt, or book_call; the pre-qualification use case must be inferred from the verdict output.

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.