Skip to main content
Glama

Check company fit

check_fit
Read-onlyIdempotent

Checks whether a company is likely to fit Datari Labs' referral criteria (30+ staff, 3+ years of kept records, UK/EU/US). Read-only: does not register anything. Use before suggesting a company register.

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": {
      "staff_count": "<staff_count>",
      "years_of_records": "<years_of_records>",
      "country": "<country>"
    },
    "name": "check_fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesCountry the company is based in, e.g. 'United Kingdom'
staff_countYesApproximate number of employees
record_typesNoOptional: kinds of records kept, e.g. ['email','chat','crm','tickets']
years_of_recordsYesHow many years of operational records (email, chat, CRM, tickets, logs) the company has kept

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, idempotentHint, destructiveHint=false and closed-world scope, so the safety bar is largely covered. The description still adds value by spelling out the evaluation thresholds and explicitly confirming 'does not register anything', removing any doubt that this is a non-mutating gate. It does not describe the shape of the verdict returned (boolean vs. score vs. reasons), which is the remaining behavioral gap.

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 short sentences, front-loaded with what is checked and followed by the usage rule and the no-side-effects guarantee. No filler or redundancy; every clause carries information.

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?

For a simple read-only eligibility check with a fully documented schema and rich annotations, the description covers purpose, criteria and workflow placement. The one thing an agent cannot infer is what the response looks like, since there is no output schema, which keeps this from a 5.

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 schema already documents all four parameters, including the optional record_types. The description echoes the thresholds that map onto staff_count, years_of_records and country but adds no format or edge-case guidance (e.g., how to handle unknown staff counts), and never mentions record_types.

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?

The description gives a specific verb and resource ('Checks whether a company is likely to fit...') and states the exact criteria (30+ staff, 3+ years of kept records, UK/EU/US). It also implicitly distinguishes itself from register_company by framing itself as a pre-check, so an agent can tell the two apart without opening either 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?

'Use before suggesting a company register' gives a clear workflow trigger and names the sibling action it precedes, which is exactly the routing an agent needs. It stops short of stating when not to call it (e.g., for an already-registered company or when criteria inputs are unknown), so it is not fully complete guidance.

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