Skip to main content
Glama

get_data_room_checklist

Read-onlyIdempotent

Data room completeness checklist for a small acquisition: documents usually expected, and four methods to find what is missing. 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_data_room_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and determinism profile is covered. The description adds content-level context (expected documents plus four missing-document discovery methods) but says nothing about output length or format, which an output schema partly covers.

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?

Two compact sentences that front-load the resource and scope with no wasted wording. The trailing getdealos.tech source URL note is of marginal value to an agent selecting or invoking the tool.

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 zero parameters, full schema coverage, annotations covering safety, and an output schema defining returns, the description supplies what an agent needs: scope, content shape, and no-input nature. Only sibling-level differentiation is thin.

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, confirmed by the empty object schema, so there are no parameter semantics to explain; baseline 4 applies. The description consistently implies static reference content requiring no inputs.

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 resource: a data room completeness checklist for a small acquisition, covering documents usually expected and four methods to find what is missing. The verb+resource is clear, though it does not explicitly distinguish itself from sibling checklists such as get_due_diligence_checklist.

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?

'For a small acquisition' gives implicit scoping guidance about when this applies. However, there is no explicit when-to-use versus when-not-to-use statement and no named alternative among the sibling 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