Skip to main content
Glama

get-case

Retrieve eDiscovery case details from Miro for enterprise organizations by providing organization and case IDs.

Instructions

Retrieves information about a specific eDiscovery case (Enterprise only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgIdYesThe ID of the organization for which you want to retrieve the case information
caseIdYesThe ID of the case you want to retrieve

Implementation Reference

  • The handler function for the 'get-case' tool that executes the logic to retrieve eDiscovery case information via MiroClient API.
    fn: async ({ orgId, caseId }) => {
      try {
        const response = await MiroClient.getApi().getCase(orgId, caseId);
    
        return ServerResponse.text(JSON.stringify(response.body, null, 2));
      } catch (error) {
        process.stderr.write(`Error retrieving case: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • Tool schema definition including name, description, and Zod input schema for orgId and caseId parameters.
    const getCaseTool: ToolSchema = {
      name: "get-case",
      description: "Retrieves information about a specific eDiscovery case (Enterprise only)",
      args: {
        orgId: z.string().describe("The ID of the organization for which you want to retrieve the case information"),
        caseId: z.string().describe("The ID of the case you want to retrieve")
      },
  • src/index.ts:203-203 (registration)
    Registration of the getCaseTool with the ToolBootstrapper instance.
    .register(getCaseTool)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Enterprise only,' which adds useful context about licensing or access restrictions. However, it lacks details on permissions needed, error handling, rate limits, or what information is returned, which are important for a retrieval tool.

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 key information ('Retrieves information about a specific eDiscovery case') and adds a necessary constraint ('Enterprise only') without any wasted words. It's appropriately sized for its purpose.

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

Completeness3/5

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

Given the tool's low complexity (2 required parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and a key constraint ('Enterprise only'), but as a retrieval tool with no annotations, it could benefit from more details on behavior or output to be fully complete.

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?

The schema description coverage is 100%, meaning both parameters (orgId and caseId) are well-documented in the schema itself. The description doesn't add any additional meaning or context about the parameters beyond what the schema provides, so it meets the baseline score of 3.

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 tool's purpose with a specific verb ('Retrieves') and resource ('information about a specific eDiscovery case'), making it easy to understand what it does. However, it doesn't explicitly distinguish this tool from its sibling 'get-all-cases' beyond the 'specific' qualifier, which is why it doesn't reach a perfect score.

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?

The description implies usage by specifying 'specific eDiscovery case' and 'Enterprise only,' suggesting it's for retrieving individual cases rather than lists. However, it doesn't provide explicit guidance on when to use this versus 'get-all-cases' or other alternatives, leaving some ambiguity for the agent.

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