Skip to main content
Glama
Sign In
Binalyze AIR MCP Server

Binalyze AIR MCP Server

Official
by binalyze
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_repositories

Retrieve all evidence repositories from the Binalyze AIR system to organize and access forensic data for incident response investigations.

Instructions

List all evidence repositories in the system

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": "list_repositories"
  }
}

Input Schema

NameRequiredDescriptionDefault
organizationIdsNoOrganization IDs to filter repositories by. Leave empty to use default (0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose whether this is a read-only operation, if it requires authentication, how results are returned (e.g., pagination), or any rate limits. The description is minimal and lacks behavioral context.

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 with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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?

For a simple list operation with one optional parameter and no output schema, the description is minimally complete. However, without annotations or output details, it leaves gaps in understanding the tool's behavior and results, making it adequate but not thorough.

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 input schema fully documents the optional 'organizationIds' parameter. The description doesn't add any parameter details beyond what the schema provides, which is acceptable given the high coverage, resulting in a baseline score.

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 verb ('List') and resource ('all evidence repositories'), making the purpose unambiguous. It doesn't distinguish from sibling tools like 'list_organizations' or 'list_cases' that follow the same pattern, but the resource specificity is adequate.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, filtering capabilities beyond the parameter, or how it relates to other list operations like 'list_organizations' or 'get_repository_by_id'.

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

Deploy Server

Other Tools