Skip to main content
Glama

start_review

Start a review of a company's documents in ISMS Copilot. Call it when the person names a company and asks for a review. Pass document_ids from the documents of get_company_overview (1 to 20). Each call starts a new review and uses one review from the plan's allowance; repeating the same call within 10 minutes returns the review it started (replayed: true). Returns review_id with status queued; follow it with get_review. The findings wait for the person's decision in ISMS Copilot (app_url). Requires workflows:write.

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": {
      "company_id": "<company_id>",
      "document_ids": "<document_ids>"
    },
    "name": "start_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNodocument_review (default), supplier_review or risk_register_review; a kind that is not available yet answers kind_off
company_idYesThe company (a UUID from list_companies)
document_idsYes1 to 20 document ids from get_company_overview documents (uploads or library documents)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well past the annotations by disclosing cost (each call consumes one review from the plan's allowance), a 10-minute replay window returning the same review with replayed: true, auth scope (requires workflows:write), and where results surface (findings wait for the person's decision at app_url). These are exactly the facts an agent needs before spending a metered, non-read operation.

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?

Six tight sentences, front-loaded with the action and trigger, then prerequisites, cost/idempotency behavior, return value, and auth. Nothing is repeated gratuitously and no sentence could be dropped without losing a decision-relevant fact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 still covers the return shape (review_id, status queued, replayed flag), the follow-up call, the metered cost, and the required scope. For a 3-parameter mutation with full schema coverage, nothing an agent needs in order to invoke it correctly is missing.

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 100%, so document_ids provenance and the 1-20 bound are already documented in the schema and the description largely restates them. The kind parameter (including the kind_off fallback) is not discussed in the description at all, so no meaning is added beyond structured fields.

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?

States a specific verb and resource ("Start a review of a company's documents in ISMS Copilot") and distinguishes itself from the follow-up reader by saying "follow it with get_review". An agent can tell this apart from list_reviews or get_review without opening any 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?

Gives a concrete trigger ("when the person names a company and asks for a review") and a prerequisite source for its main argument (document_ids from get_company_overview), plus the continuation tool. It lacks an explicit when-not clause, e.g. what to do if a review already exists or only one ad-hoc document is meant, so it is strong but not exhaustive.

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.