Skip to main content
Glama

list_reviews

Read-onlyIdempotent

List a company's reviews in ISMS Copilot, newest first: kind, status, findings and undecided counts, and the documents reviewed. 20 per page by default (at most 100); pass next_cursor as cursor for the next page. On the free plan only the latest result is listed. Requires workflows:read.

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>"
    },
    "name": "list_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (default 20, at most 100)
cursorNoOptional: next_cursor from the previous page
company_idYesThe company (a UUID from list_companies)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses ordering (newest first), page-size default and hard cap of 100, the exact pagination token contract, and a plan-dependent truncation behavior that an agent would otherwise never infer.

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 tightly packed sentences with the resource and ordering front-loaded, then return fields, then pagination and constraints. No filler and every clause carries information.

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?

No output schema exists, so the description compensates by listing the returned fields; it also covers permission requirements, plan limits, and pagination, leaving nothing an agent needs in order to call this correctly.

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 coverage is 100%, so the baseline is 3, but the description adds the pagination flow ("pass next_cursor as cursor for the next page") and repeats the effective default/maximum page size, giving an agent the operational meaning of the parameters rather than just their 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?

States a specific verb and resource ("List a company's reviews") and then enumerates the fields returned (kind, status, findings, undecided counts, documents reviewed), which makes the result shape unambiguous and distinguishes it from the singleton get_review.

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 clear calling context: scope requirement (workflows:read), plan-based truncation on free plans, and the pagination loop via next_cursor. It stops short of naming an alternative tool (e.g. get_review for a single review), so it lacks explicit exclusions.

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.