Skip to main content
Glama

get_due_diligence_checklist

Read-onlyIdempotent

Due diligence checklist for buying a small company. deal_type: 'general' (any small business), 'software' (SaaS or data company: recurring revenue, code and IP, data rights, security) or 'sba' (SBA 7(a) financed deal: QoE threshold and coverage test). Ends with the getdealos.tech source URL.

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

Input Schema

NameRequiredDescriptionDefault
deal_typeNogeneral

Output Schema

NameRequiredDescriptionDefault
resultYes

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 declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real context beyond that: the returned checklist contents differ substantially by deal_type (recurring revenue/IP/data rights/security for software; QoE threshold and coverage test for SBA) and the output ends with a source URL, which tells the agent what to expect in the payload.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Compact and front-loaded — purpose first, then the branch semantics in one dense parenthetical. The trailing sentence about the getdealos.tech source URL is slightly awkward but short and informative, so little 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 one optional enum parameter, full annotations, and an output schema, this is nearly complete: an agent knows what it gets, how the variant changes it, and that it is a safe read. Only the missing sibling differentiation and the unstated default keep it from being fully self-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?

Schema description coverage is 0%, so the description must carry the parameter meaning, and it does: all three enum values are explained with the substantive content each unlocks. The only shortfall is that it never states the default explicitly (the schema supplies default='general'), leaving the no-arg case to inference.

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?

States a specific resource and scope: 'Due diligence checklist for buying a small company', with the deal_type variants spelled out. It does not differentiate itself from sibling checklists such as get_due_diligence_checklist vs get_drive/software alternatives like get_diligence or get_due_diligence_checklist — notably get_data_diligence_checklist exists as a sibling and is not mentioned, so an agent must infer which checklist applies.

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?

Usage is implied by 'for buying a small company' and the enum parentheticals tell the agent which variant to pick for SaaS/data or SBA-financed deals. There is no explicit when-not guidance and no named alternative (e.g. get_data_room_checklist) to route between similar checklist tools.

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