Skip to main content
Glama

get_cim_review_guidance

Read-onlyIdempotent

What a buyer should check in a CIM (Confidential Information Memorandum) and which documents to compare it against. 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_cim_review_guidance"
  }
}

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, idempotentHint, non-destructive and a closed-world scope, so the safety profile is covered. The description adds one output trait — that the content ends with the getdealos.tech source URL — but says nothing about the format or structure of the guidance beyond that, so the added behavior is modest.

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 short sentences, front-loaded with the subject (what to check in a CIM) before the comparison scope. The final clause about the source URL is the weakest piece — mildly promotional and less useful than the rest — but it is a single short clause and does not bloat the definition.

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?

An output schema exists and there are no parameters, so the description does not need to enumerate return fields. For a simple static guidance tool it conveys enough to call correctly, though it could note whether the guidance is static or deal-specific.

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, so the baseline of 4 applies; there is no parameter meaning the description needs to supply. The description correctly implies a parameterless, static guidance lookup with no filtering.

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 names a specific resource — what a buyer should check in a CIM — and adds the scope of comparing it against other documents, so the agent knows this is substantive review guidance rather than a generic checklist. It does not explicitly differentiate itself from the sibling checklists (get_data_room_checklist, get_due_diligence_checklist), which keeps it below a 5.

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 only implied: an agent can infer this applies when a buyer is examining a CIM. There is no explicit when-to-use statement, no when-not-to-use, and no routing to the related due-diligence or data-room checklist siblings.

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