Skip to main content
Glama
Sign In
OpenCTI MCP Server

OpenCTI MCP Server

by zxzinn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_file_by_id

Retrieve file information from OpenCTI using its unique ID. Access cyber threat intelligence data for analysis and investigation.

Instructions

根據ID獲取檔案資訊

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": {
      "id": "<id>"
    },
    "name": "get_file_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes檔案ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden. It does not disclose behavioral traits such as read-only nature, required permissions, error handling (e.g., if ID not found), or rate limits. The description adds no detail beyond the name.

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, concise sentence with no unnecessary words. It is front-loaded and efficient.

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 get-by-id tool with one parameter and no output schema, the description is minimally adequate. However, it lacks details on return values, error conditions, or any behavioral nuances, leaving gaps for an AI agent.

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 coverage is 100% and the parameter 'id' is described. The description reinforces that the ID is used, but adds no additional meaning beyond the schema. Baseline 3 applies.

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?

The description clearly states the tool's action: retrieving file information by ID. It distinguishes itself from sibling tools like list_files or search tools by specifying the retrieval method (by ID).

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 when a file ID is available, but lacks explicit guidance on when to use this tool versus alternatives like list_files for browsing. No when-not or alternative references are provided.

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