Skip to main content
Glama

get-all-legal-holds

Retrieve all legal holds for a specific case within an organization to manage compliance and legal requirements.

Instructions

Retrieves the list of all legal holds within a case (Enterprise only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitYesThe maximum number of items in the result list
orgIdYesThe ID of the organization for which you want to retrieve the list of legal holds
caseIdYesThe ID of the case for which you want to retrieve the list of legal holds
cursorNoCursor for pagination

Implementation Reference

  • The main handler function that implements the tool's logic. It constructs a query, calls the Miro API's getAllLegalHolds method, and handles the response or error.
    fn: async ({ limit, orgId, caseId, cursor }) => {
      try {
        const query: any = {};
        if (cursor) query.cursor = cursor;
    
        const response = await MiroClient.getApi().getAllLegalHolds(limit, orgId, caseId, query);
    
        return ServerResponse.text(JSON.stringify(response.body, null, 2));
      } catch (error) {
        process.stderr.write(`Error retrieving legal holds: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • The ToolSchema definition including the tool name, description, and Zod schemas for input arguments (limit, orgId, caseId, cursor).
    const getLegalHoldsTool: ToolSchema = {
      name: "get-all-legal-holds",
      description: "Retrieves the list of all legal holds within a case (Enterprise only)",
      args: {
        limit: z.number().describe("The maximum number of items in the result list"),
        orgId: z.string().describe("The ID of the organization for which you want to retrieve the list of legal holds"),
        caseId: z.string().describe("The ID of the case for which you want to retrieve the list of legal holds"),
        cursor: z.string().optional().nullish().describe("Cursor for pagination")
      },
  • src/index.ts:103-103 (registration)
    Import of the get-all-legal-holds tool module.
    import getLegalHoldsTool from './tools/getAllLegalHolds.js';
  • src/index.ts:204-204 (registration)
    Registration of the get-all-legal-holds tool with the ToolBootstrapper instance.
    .register(getLegalHoldsTool)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'Enterprise only', hinting at access restrictions, but fails to disclose key behavioral traits like whether this is a read-only operation, potential rate limits, pagination behavior (implied by 'cursor' parameter but not explained), or error conditions. The description is too sparse for a tool with multiple parameters and no output schema.

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?

The description is a single, efficient sentence that front-loads the core purpose ('Retrieves the list of all legal holds') and includes essential context ('within a case (Enterprise only)'). There is no wasted verbiage, making it highly concise and well-structured for quick comprehension.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (4 parameters, no annotations, no output schema), the description is incomplete. It lacks details on behavioral aspects (e.g., pagination, permissions), output format, or error handling. While concise, it doesn't provide enough context for an agent to use the tool effectively beyond basic purpose, especially with no structured annotations to compensate.

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 description coverage is 100%, so the schema fully documents all parameters (limit, orgId, caseId, cursor). The description adds no additional parameter semantics beyond implying retrieval is scoped to a case and organization, which is already covered in schema descriptions. Baseline score of 3 is appropriate as the schema does the heavy lifting.

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 clearly states the action ('Retrieves') and resource ('list of all legal holds within a case'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'get-legal-hold' (singular) or 'get-legal-hold-content-items', which might retrieve specific holds or their contents, leaving some ambiguity about sibling relationships.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides minimal guidance by specifying 'within a case (Enterprise only)', indicating a context and restriction, but it lacks explicit when-to-use instructions, alternatives (e.g., vs. 'get-legal-hold'), or prerequisites. No clear usage scenarios or exclusions are mentioned, making it insufficient for optimal tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/k-jarzyna/mcp-miro'

If you have feedback or need assistance with the MCP directory API, please join our Discord server